Fix: forks should not branch trigger deletion #23
Conversation
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
SvanBoxel
added a commit
that referenced
this pull request
Sep 12, 2018
* Added test case * Fix: forks should not branch trigger deletion
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.
Forks should not trigger branch deletion.
This bug was introduced because the code didn't make a difference between PR's that came from a fork or the original repo. Then it grabbed the current repo name and the branch name of the fork. This could result in something like
<currentRepo>/master. A merge of such a PR could trigger the delete event of the master branch where this app was installed. Not something we want.Fixes #21