Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
repo_checker: provide --post-comments option on project_only subcommand (and cleanups). #1042
Deployment as service should be blocked by #1029 even though old
Invocation is simple:
I went ahead and did a manual run in order to get the cleanup started especially with SLE/Leap 15 branching from Factory. The script produced
To be clear this approach:
I debated posting bugs to bugzilla, but that would be a fair bit more work especially considering the clean comments api we have for avoiding useless updates, but ensuring a single comment. I did envision shared bugs between two packages that have file conflicts which would be neat, but this just duplicates those messages to both packages.
A hash representing the binaries and number of issues is generated to avoid updating comment for version updates or release increments while still properly picking up new or changes to existing issues.
Depending on how this works out and opinions this approach can be broadened for the rest of repo_checker or at minimum include for duplicate binary checks.
After the recent fixes that were hiding all
See dashboard/repo_checker for an updated report.
The end result are package comments like the following on devel:languages:ruby:extensions/rubygem-celluloid.
One caveat being that there is no simple way of removing these comments since the OBS comment API does not provide a way of querying all comments by a user so each devel project would have to be scanned. Alternatively, on accept comments for all effected packages could be removed. I would expect these comments to be relatively rare once the new
As seen in this example the comments are resulting in fixes!
Re-ran today for stats