Remove remote branches only for origin after accepting work
#228
Conversation
This file contains 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
A user may accept work from forked remotes. In this case, it's possible that a remote fork provides only pull permissions. And, in order to prevent errors, the removal is enabled only for `origin` - is a user accepts work, it has a write permissions to `origin`. #171
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A user may accept work from forked remotes. In this case, it's possible
that a remote fork provides only pull permissions. And, in order to
prevent errors, the removal is enabled only for
origin- is a useraccepts work, it has a write permissions to
origin.#171
The contribution:
CONTRIBUTING.md > Committing the changesrulesREADME.md > Hands-on development notes@bees-hive/elegant-git-maintainers, please review.