This message was deleted.
# bug-reportss
Slackbot
05/02/2023, 6:35 PMThis message was deleted.
j
Jacob Gold
05/02/2023, 6:36 PMSorry you're running into this! Is your stack based on the default branch?
k
Krishna Vudata
05/02/2023, 6:36 PMyes
Krishna Vudata
05/02/2023, 8:18 PMfwiw I wasn’t encountering a problem with stack merging last week, and we haven’t changed our required status checks since then
j
Jacob Gold
05/02/2023, 9:16 PMWhat is the expected behavior here, that CI doesn't run until you trigger the merge?
k
Krishna Vudata
05/03/2023, 4:23 PMCI doesn’t run until you trigger the merge?not exactly - the expectation is that it doesn’t run until the PR’s base branch is set to the default branch. Essentially, this is a cost saving strategy to minimize unnecessary runs I would expect 1. Graphite allows me to enqueue the stack merge if the required status checks according to GitHub are passing (i.e. it respects how required status checks have been configured in the branch protection rules for the current base branch of the PR) 2. when the base branch is merged into the default branch and the “current’ feature branch’s base is switched to the default branch, then GitHub will consider the check to be required and trigger it (if needed)
Krishna Vudata
05/03/2023, 7:54 PMfor now, I’ve managed to work around this issue by setting our github workflow to trigger regardless of the PR’s base branch, and have the jobs in the workflow skip (i.e. no-op)
looks like Graphite is happy now that a status (of skipped) is being reported