Conversation
That's when the config mirror matches the current config and there's nothing to do.
Previously if you initially set this up on a project at a time when the config's already been changed, that wouldn't cause a PR to be created: you'd have to wait until the next config change.
Previously if the config-only branch existed then it was used, even if it was connected with a rejected PR. Not it only adds to the existing branch if there's an open PR associated with it.
andriokha
force-pushed
the
updates
branch
2 times, most recently
from
July 1, 2026 19:22
0f1e79e to
01e1c31
Compare
actions/cache -> 6.0.0 actions/checkout -> 7.0.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See individual commits