Skip to content
Sign up

flagon-io/g1t

public
00

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

gitagentscloudflarerustforgemcp
syntaqxMerging a pull request that has fallen behind waits for the required checks on the commit that brings it up to date, and a merge the repository does not answer says so instead of hanging. Pressing Merge on a pull request behind its target brought it up to date and then landed it at once, asking to skip its checks; a ruleset that requires checks and does not allow skipping them (flagon-io/g1t's "Main stays deployable", CI required) refused that, so every catch-up-then-merge there stopped at "Needs you" with "The required check CI from actions has not reported on its latest commit". Now the merge waits: once the catch-up push arrives, it lands as soon as every required check passes on that new commit (decided as each of the commit's checks finishes, statuses.rs store_status), at once when none are required, and when a required check fails there it stops with "It was brought up to date, but the required check CI failed on that commit, so it was not merged. Push a fix, then merge again." Two checks finishing together land it once (the waiting merge is taken in one statement). A merge asked to go past failing checks, where the repository allows that, still lands without waiting. The wait stands for three hours (the catch-up push still for 30 minutes); a pull request g1t is seeing through shows it as Checking. The merge box says "Merging once checks pass: Brought up to date with main. It lands once the required check CI passes on that commit.", then "Landing now."; while it is still being brought up to date it says it lands once the required checks pass on that commit, when there are any.