I view MUSL builds as an "implementation detail" of the official Docker
image. As such, I don't really think they're worth mentioning in the
build matrix on the main README. Most users likely won't care about it
and I want to reduce clutter / confusion.
The builds themselves, however, are still always available on each
release for those that do want them.
Can be used to quickly and conveniently get a list of release profiles
(and their Trash IDs) so you know what to add in your YAML config under
`release_profiles`.
Squashed commit of the following:
commit 673f4b7441d910cf25dce6842552a06bf5f76490
Author: Robert Dailey <rcdailey@gmail.com>
Date: Wed Nov 10 12:37:55 2021 -0600
Add SonarCloud integration
commit 5dfe5cf7a2c2a96ecdc0c684c605334460efbf73
Author: Robert Dailey <rcdailey@gmail.com>
Date: Wed Nov 10 12:46:40 2021 -0600
Reformat YAML
commit d210104ffee6fea81304312588e9fa89fb1a86f0
Author: Robert Dailey <rcdailey@gmail.com>
Date: Wed Nov 10 12:46:16 2021 -0600
Remove stale comments in build.yml
commit 66f18519c39b1cece888d7028cd2056d2f8dfbe3
Author: Robert Dailey <rcdailey@gmail.com>
Date: Wed Nov 10 12:44:28 2021 -0600
Set up schema for build.yml
These sections are not particularly useful anymore since the program has
matured. Going forward I plan to track roadmap items and limitations as
issues in Github.
I also fixed a minor typo in the getting started section.
Features list now shows that "optional" terms in the release profile
guide are ignored by default.
Limitations section now states that there is currently no mechanism to
selectively include optional terms.
The `--strict-negative-scores` option will take any negative preferred
term scores and move those terms to the "Must Not Contains" (ignored)
field of the release profile.