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
update/update-reset: warn when no origin remote #13187
Conversation
Review period will end on 2022-04-26 at 12:01:51 UTC. |
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.
Nice work so far!
Thanks for the suggestions, Mike! |
Thanks again @maxim-belkin! |
Review period ended. |
@MikeMcQuaid, I don't think that changes introduced in this PR can cause the failure observed in "CI/test everything". I re-ran the workflow once and the error message changed. Should I rebase it or re-run the workflow again? |
@maxim-belkin Try to rebase and try again. If it still fails: you may have accidentally broken |
Current situation with update.sh & update-reset.sh: Upon creating a new tap and before adding remote 'origin' to it, running `brew update` produces multiple cryptic error messages. This change converts these cryptic Git messages into clear warnings about absent remote 'origin'. How to test: 1. Create a new tap using `brew tap-new` 2. Run `brew update`
Co-authored-by: Mike McQuaid <mike@mikemcquaid.com>
9699b95
to
13735bc
Compare
🎉 |
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?Explanation of changes
Current situation with update.sh & update-reset.sh:
Upon creating a new tap and before adding remote 'origin' to it, running
brew update
produces multiple cryptic Git error messages. This change converts these cryptic Git messages into clear warnings about absent remote 'origin'.How to test:
brew tap-new
brew update
I also noticed that variable "option" in
homebrew-update-reset
was not declared as "local", so I went ahead and fixed it.