Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
precommit warns on main + instructions for fix#26171
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Oh, you managed to beat me to the PR.
Uh oh!
There was an error while loading.Please reload this page.
😅 you're welcome to take over |
Uh oh!
There was an error while loading.Please reload this page.
1384342
to28d6a26
Comparedo not love that this is running away from me/growing in scope, but since it is are there any other branches that I should include? (like doc or whatever) or is main the only one that's a problem. |
So this pr now has: |
8631d19
to34d8fc3
CompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
617c465
todf6331d
CompareThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Minor corrections.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
+ instructions for fix in docsCo-authored-by: Greg Lucas <greg.m.lucas@gmail.com>Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
Uh oh!
There was an error while loading.Please reload this page.
Added a branch protect rule to the pre-commit so that it complains if you try to commit directly to main. I figure folks who really need to push to main also know how to work around it. based on convo in call w/@greglucas
Not quite sure this is the best way to handle the error message but figure we need to give folks a fix.
Is a replacement for#26170 which I'm not sure how I accidentally created directly on the repo.