-
Notifications
You must be signed in to change notification settings - Fork 12
🐛 Skip branch push when a run produces no commits #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| kind: bugfix | ||
| description: > | ||
| Harness skips the branch push when a run produced no commits beyond its | ||
| checkout point, so no-op, refused, and skill-less runs no longer litter | ||
| remote repositories with empty branches. A workflow stage that adds no | ||
| new commits on the shared branch skips its push the same way. Run | ||
| notices report a skipped push honestly (no changes to push) instead of | ||
| claiming results landed on the branch. |
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: this check looks redundant with the
NoErrAlreadyUpToDateswallow below, but it's actually the only guard that prevents empty branch creation on the remote. When the branch doesn't exist yet,go-git'sPushContextgenerates a push command (ZeroHash → local HEAD), soNoErrAlreadyUpToDatenever fires.A short comment above the
if baseSHA != ""block explaining this distinction would prevent a future maintainer from removing it as belt-and-suspenders.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call — comment added in b7c7c7e capturing exactly that: on a missing remote branch PushContext sends a create command (ZeroHash → HEAD), so NoErrAlreadyUpToDate never fires and this guard is the only thing preventing empty branch creation.