You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main reason is, master branch protection rule in this repo requires pull-requests, approvals, CI checks etc, which is not suitable for goreleaser.
Second reason is, if we keep the formula in a repo with homebrew- prefix, s5cmd brew installation will be a single step, which is nice. For example, if we have homebrew-tap repo with a structure like below:
homebrew-tap
└── Formula
└── s5cmd.rb
brew install peak/tap/s5cmd will directly install the package from the repo without tapping.
This change will affect how users install from homebrew.
Previously, it was:
brew tap peak/s5cmd https://github.com/peak/s5cmd
brew install s5cmd
Now it'll be:
brew install peak/tap/s5cmd
Fixes#356
This change will affect how users install from homebrew.
Previously, it was:
brew tap peak/s5cmd https://github.com/peak/s5cmd
brew install s5cmd
Now it'll be:
brew install peak/tap/s5cmd
Fixes#356
The main reason is, master branch protection rule in this repo requires pull-requests, approvals, CI checks etc, which is not suitable for
goreleaser
.Second reason is, if we keep the formula in a repo with
homebrew-
prefix, s5cmd brew installation will be a single step, which is nice. For example, if we havehomebrew-tap
repo with a structure like below:brew install peak/tap/s5cmd
will directly install the package from the repo without tapping.https://docs.brew.sh/Taps#repository-naming-conventions-and-assumptions
The text was updated successfully, but these errors were encountered: