A pull request won't merge
A task's pull request shows on its page under Pull requests, as merged, open or closed. On a project whose merge lane is on, the lane tests and merges each pull request; its work is under Audit > Merge lanes: pick the project in the Project filter. What the tab shows is in Audit.
The lane's tests failed
Symptom: on Merge lane, the pull request's row reads Failed, with Tests failed.
Cause: the project's Full gate command failed on the merged result.
Fix: you don't have to do anything. Jaah queues the task again with the lane's verdict, and the runner fixes the failing tests, pushes and sends the pull request back to the lane. Open the task to follow it. If it keeps failing on a test unrelated to the change, check the Flakes tab, and fix or skip that test on the integration branch.
It conflicts with the branch
Symptom: the row reads Failed with Merge conflict or Branch behind.
Cause: other work merged into the integration branch since the pull request was made, and the two changes overlap, or the repository requires branches to be up to date.
Fix: as for failed tests, Jaah sends the task back to its runner, which updates the branch, resolves the conflict and resubmits. Conflicts that only add lines are resolved by the lane itself.
The lane is held or the branch is red
Symptom: the lane's dot reads Held, or a red icon says the integration branch is red.
Cause: Held means one lane run is stopped, asking or reset, and no other run starts while it stands. A red branch means tests fail on the integration branch itself, so nothing merges until a task fixes it.
Fix:
- Point at the Held dot: it names the run.
- Open that run's task. If it is Asking, answer it; if it is stopped, select Start to resume the lane.
- If you don't need that run, open its ⋯ menu and select Complete to let the next one start.
- For a red branch, open the task the red icon names and follow it to Done. The lane starts again on its own.
The lane can't merge at all
Symptom: the row's failure reads No forge login, or the lane says Push is off for this project, so the lane cannot merge.
Cause: the person the task runs as has no working Git account, or the project is read only.
Fix:
- No forge login: the person who started the task opens their profile, then the Git section, and selects Reconnect on a row that says Needs reconnect, or connects an account. For the lane's own tasks, an Org Owner or Org Admin sets Run jobs as under Advanced in the project's Settings › General.
- Push is off: an editor of the project selects Turn on Push, or clears Read only under Settings › Branches, and saves.
The pull request stays open with no lane
Symptom: the project's lane under Audit > Merge lanes is empty or off, and the pull request stays open.
Cause: the repository's own rules, such as a required review or a required check, hold it.
Fix: open the pull request on your Git host and read why it can't merge. Approve it, or fix the failing check, and it merges. To have Jaah merge without a review, change the branch's protection on your Git host.
Related
- Projects — the Integration branch, gates and Read only.
- Read a task's result — where a task's pull request shows.
- A task is stuck or failed — when the task itself doesn't finish.