-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated Review #3
Comments
I propose that the items following should be automated when a user PRs a new module package manifest. Any test failures would consequently block merging until resolved.
Other potential items:
Some of these items are inspired by the automation utilized in the winget-pkgs repository for their submission validation. |
We could additionally check if the latest supported bhud crashes when the bhm with all its dependencies gets loaded. It would be a lot of work to implement this though. |
I absolutely see value to that, so I don't want to discount it, but you're right — it would be some extra work. I suspect that is something we could implement down the road, though. |
The first implementation of this is complete. It is not yet triggered automatically, but does cover the following tests:
It also hosts decompiled source and ref contents in a repo to make reviewing code changes easier. |
Automation through CI should be the primary method of PR review to ensure a minimum level of quality in submitted manifests, reduce the chance for human mistakes, and reduce the workload of reviewers.
The text was updated successfully, but these errors were encountered: