-
Notifications
You must be signed in to change notification settings - Fork 109
Open
Labels
Good First IssueIssue that is good for someone new to the Solus project to try to tackleIssue that is good for someone new to the Solus project to try to tackleType: ChoreNot a feature or a bugNot a feature or a bug
Description
A monitoring.yaml
file is used by Solus package to enable automatic scanning for new releases and security advisories. It is included in the directory of the relevant packages alongside package.yml
, pspec*.xml
, and MAINTAINERS.md
. Read more about it on our Help Center.
You can find all the packages that are still without monitoring.yaml
by running this command:
# Replace solus-builds for the directory you have in your system
cd solus-builds/packages
find . -maxdepth 2 -mindepth 2 ! -exec sh -c 'test -e "$1"/monitoring.yaml' sh {} \; -print
Guidance on fixing
- One commit per package, but multiple commits (packages) on one Pull Request is OK
- No need to bump and rebuild the package, our build tooling does not read
monitoring.yaml
- Be sure to check for a CPE, even though many packages will not have one.
The list
307029372686260423001923189817171419 packages left- https://gist.github.com/malfisya/696f92c7555e043bfc0499c26aad8f58
Metadata
Metadata
Assignees
Labels
Good First IssueIssue that is good for someone new to the Solus project to try to tackleIssue that is good for someone new to the Solus project to try to tackleType: ChoreNot a feature or a bugNot a feature or a bug
Type
Projects
Status
Ready