check-pr

Topics in the source

• Check PR
• Inputs
• Instructions
• 0. Detect platform
• 1. Identify the PR/MR/CL
• 2. Fetch PR/MR/CL details
• 3. Wait for pending checks
• 4. Require a fresh Greptile review for the current head

Analyze a pull request (GitHub), merge request (GitLab), or shelved changelist (Perforce) for review comments, status checks, and description completeness, then help address any issues found. PR/MR/CL number (optional): If not provided, detect the PR/MR for the current branch, or the default pending changelist for p4. First check if the user is working in a Perforce depot by looking for a .p4config file or P4CLIENT/P4PORT environment variables: For self-hosted GitLab instances whose hostname doesn't contain "gitlab", the user can override by passing --vcs gitlab as an input. For Perforce, the user can override by passing --vcs perforce. If a number was provided, use it. Otherwise, detect it: GitHub: GitLab: Perforce: Key field differences between platforms: GitHub: number, headRefName, headRefOid GitLab: iid, sourcebranch, sha Perforce: changelist number (CL), shelved files for in-review CLs GitHub: GitHub PRs are also issues, so general PR comments live on the issue comments endpoint. Greptile may edit a single general PR comment on each review cycle instead of creating a new review or comment. Always inspect the latest Greptile-authored general comment by updatedat, including any

This is an excerpt. Refer to the complete source and its current requirements.