rulesets/nixpkgs: delete accidentally created protected branches #137
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
These branches had been created with a protected prefix in the past - and thus accidentally became protected. This also meant that no pushes were possible eventually - and thus these branches were quickly abandoned. This PR intends to add these temporarily to the ruleset as exceptions - to then delete the branches immediately. Thus, this PR doesn't need to actually be merged. Importing the ruleset, deleting the branches, and then reverting the ruleset to its previous state should be enough.
Member
|
Done as suggested, the branches are now deleted, thank you! |
Contributor
Author
|
@infinisil I found one more, which followed an odd naming scheme that didn't match my search: staging.patchShebangs |
Member
|
Done :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
These branches had been created with a protected prefix in the past - and thus accidentally became protected. This also meant that no pushes were possible eventually - and thus these branches were quickly abandoned.
This PR intends to add these temporarily to the ruleset as exceptions - to then delete the branches immediately. Thus, this PR doesn't need to actually be merged. Importing the ruleset, deleting the branches, and then reverting the ruleset to its previous state should be enough.
Now that #132 prevents the accidental creation of new cases, we can do this.