Don't run repository sync on branch deletion. #3
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.
Fixed an issue with the
sync
action that propagates changes from Github to Bitbucket. The problem was thatmain
branch were propagated to Bitbucket.So when a non-
main
branch was created in Github, it was not replicated in Bitbucket (only themain
branch). When such a branch was deleted in Github, thesync
action tried to delete it in Bitbucket as well, where it didn't exist, causing an error.I've fixed this by disabling the
delete
trigger in thesync.yml
action. As we only want to keepmain
in sync (and won't delete this branch at any point), thedelete
sync isn't necessary.The alternative would be to sync all branches to Bitbucket, even short-lived branches for pull-requests.