-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
4 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,20 +30,18 @@ brew install qaware/tap/protocurl | |
|
||
## Formulae maintainer | ||
|
||
_TL;DR Deploy only your `Formula/[foo]@[major].[minor].rb` files and enjoy the benefits of the CI!_ | ||
_TL;DR Deploy only your `Formula/[foo].rb` and `Formula/[foo]@[major].rb` files. | ||
|
||
If you want to push your own `Formulae` these are the steps: | ||
|
||
* Get a `Deploy Token` for your repo/CI (can be requested by the maintainers of this tap-repo) | ||
* Set up your CI to push the ruby files to `Formula`. | ||
You can push either of these `Formulae`: | ||
`foo.rb`, `[email protected]`, `[email protected]` | ||
**Other formats (with bugfix version or with buildpostfix) will be removed by the CI.** | ||
**Other formats (with bugfix version or with buildpostfix) may be removed by the CI in the future.** | ||
This behaviour is accordingly to [brew Versions](https://docs.brew.sh/Versions). | ||
* The CI of `qaware/homebrew-tap` will create the `latest` (`Aliases/foo.rb`) symlink and the `major` (`Aliases/[email protected]`) symlink. | ||
This behaviour provides an easy way to only push one `Formulae` and still have a full version selection available. | ||
If you want to manage these "high-level" versions on your own, the CI will not create aliases if a `Formulae` is present. | ||
`Formulae` have precedence over `Aliases`. | ||
* The CI of `qaware/homebrew-tap` will update the README.md TOC. | ||
* You can use the `Aliases` folder as you want, if you stay within the brew conventions. | ||
|
||
## Maintainers | ||
|
||
|