-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
🚀 Feature: A script to revert changes made via GitHub API #1379
Comments
Yeah it's annoying 😕 I've been inconvenienced by this before. It would be nice if the previous state of things could be stored somewhere. Proposal: how about adding something to the output at the end of
...where the script is a file written to disk?
I think this will still be an issue there? Since you might not want to preserve rulesets changes. |
Just to satisfy my own curiosity, what was the nature of the changes made? And to which branch? |
Branch protections get set up on the create-typescript-app/src/steps/initializeGitHubRepository/initializeBranchProtectionSettings.ts Line 12 in 3a8c7c0
|
"We will protect you whether you like it or not!" |
I wound up deleting my
Right, I misunderstood this GitHub feature. I thought it let you configure rulesets via code, which really would solve the problem. Still, I wonder if you could create a new ruleset and let the user delete whatever existing branch protections they had before once they're ready to commit. At least then the new ruleset wouldn't be overriding anything. |
Bug Report Checklist
main
branch of the repository.Overview
I ran
npx create-typescript-app
on https://github.com/danvk/literate-ts and created a PR, but I didn't merge it. I was surprised to see that changes had been made to my repo via the GitHub API (branch protection rules) independently of that PR.I'll manually revert them, but it would be nice if these changes could be made / reverted more easily via a script.
Additional Info
Would likely be fixed by #1309. Feel free to close this as a dupe if that's a feasible solution.
The text was updated successfully, but these errors were encountered: