-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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 CONTRIBUTING.md #16511
Update CONTRIBUTING.md #16511
Conversation
brew install vitorgalvao/tinyscripts/cask-repair | ||
cask-repair --help | ||
|
||
# use to update "cask-to-update" |
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.
could use a better "placeholder name" here
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.
No issues with the name, but the quotes took me a second. Something like <cask-to-update>
{{cask-to-update}}
might be clearer. If you’re unhappy with the name, how about outdated-cask
?
Using cask-repair covers #16464 - not sure where else to mention appcast updates, as the rest is really about new casks. |
brew install vitorgalvao/tinyscripts/cask-repair | ||
cask-repair --help | ||
|
||
# use to update <outdated-cask> |
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.
Since you’re using $github_user
on the command, why not follow the same pattern for the cask? I.e.:
outdated_cask=<the-cask-i-want-to-update>
cd "$(brew --repository)/Library/Taps/caskroom/homebrew-cask"
cask-repair --pull origin --push $github_user $outdated-cask
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.
Done and squashed
|
||
```bash | ||
# install and setup script - only needed once | ||
brew install vitorgalvao/tinyscripts/cask-repair |
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.
Just renamed the repo to vitorgalvao/tiny-scripts
(I wanted that name from the start, but at the time homebrew didn’t allow hyphens in tap names). The old name still works (looks like github is handling the redirection well), but still the new name should be used.
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.
Just "updated" my tap. All seems to be good.
[~] > brew untap vitorgalvao/tinyscripts
[~] > brew tap vitorgalvao/homebrew-tiny-scripts
[~] > brew uninstall cask-repair prfixmaster fastmerge
Uninstalling /usr/local/Cellar/cask-repair/0.13.3... (4 files, 11.5K)
Uninstalling /usr/local/Cellar/prfixmaster/0.4... (4 files, 7.4K)
Uninstalling /usr/local/Cellar/fastmerge/0.7.1... (4 files, 7.2K)
[~] > brew install cask-repair prfixmaster fastmerge
==> Installing cask-repair from vitorgalvao/tiny-scripts
==> Cloning https://github.com/vitorgalvao/tiny-scripts.git
{snip)
The Formulas repo needs a README update, but otherwise okay
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.
The Formulas repo needs a README update
Nice catch. Thank you.
No need to reinstall, though, I’ve tried it, and homebrew seemed to still identify them correctly.
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.
CONTRIBUTING updated. If it looks good, we can merge this
@zmwangx Here's the updated documentation with |
👍 LGTM, except one minor thing: |
@zmwangx |
Remove extra sections Add Updating Cask section Revise style guide
@vitorgalvao I added a (slight) disclaimer - though Let me know if the wording is too strong, either way. |
Cool 👍 Just to make sure, are there any half interpolated URLs, e.g., |
I’m fine with that. But any case Also (and to also reply to)
Lets not forget So yes, @zmwangx, |
Yes. |
First pass at #16373
Comments welcome. cc @caskroom/maintainers