docs: Clarify two separate build time limits in GitHub integration docs

[promptless]

Open this suggestion in Promptless to view citations and reasoning process

Updated the Limitations section to clarify that the GitHub integration has two separate time limits: a 160-minute total build window for the entire process (cloning, building, uploading, testing), and a 30-minute Docker build timeout for the docker build step specifically. Also added the specific error message users see when hitting the Docker timeout, to help users understand which limit they've hit.

Trigger Events

Internal discussion about a Slack message link shared by Mo King, with Promptless bot responding to process the request.

Promptless Research (1 Slack conversation)

• Opened Slack conversation

Agent Response

I've completed the documentation update to address the customer confusion about GitHub integration build timeouts.

Summary

Based on the Slack thread in #team-support-eng-escalations, multiple customers were confused because the documentation only mentioned the 160-minute build time limit, but their builds were failing at 15-30 minutes. This was happening because there are actually two separate timeouts:

1. Total build window (160 minutes): The entire GitHub build process - cloning, building, uploading, and testing
2. Docker build timeout (30 minutes): The docker build step specifically

What I changed

Updated the Limitations section in the GitHub integration docs to clearly explain both time limits and include the specific error message users see when they hit the Docker build timeout:

Build exceeded maximum time limit of 1800 seconds (30.0 minutes)

This helps users understand which limit they've hit and provides guidance to pre-build images locally if their dependencies or model weights take longer than 30 minutes to download and install.

Suggestion created

Title: Clarify two separate build time limits in GitHub integration docs

The suggestion is ready for your review. The change is concise and directly addresses the customer feedback Anamika documented in the support escalation thread.

---

Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.

If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)