-
Notifications
You must be signed in to change notification settings - Fork 523
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
Mapchecker #810
Mapchecker #810
Conversation
…4 into mapchecker
Proooobably should also @MagnusCrowe here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going to wait for others to also approve this, seem fine by me.
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
try to keep ship file updates to their own PRs, else you will end up in conflict hell.
Can do, will add all current violations to technical debt list of the whitelist to prevent this PR from murdering the success state of other PR's. |
This reverts commit 20abe7b.
…to demonstrate this works mostly
Gonna stop touching this PR now. I feel like the items that were marked |
About the PR
This is a map checker! @dvir001 @Cheackraze
Essentially this allows us to automatically check shuttle/POI/... PR's for prototypes which are "suspicious" for that map, automatically as a github workflow.
Additionally, the following was the output on script creation, after some heavy cleanup:
All of these have either been tagged as allowable for this shipyard category, or have been temporarily whitelisted (technical debt).
Why / Balance
Automation of a menial task which can overlook things in the hands of man.
Technical details
.github/mapchecker/mapchecker.py
.github/mapchecker/config.py
due to their complex nature.Media
No. I have not. For my sanity I will do this later.
Breaking changes
Any other PR that modifies any of these ships will likely be merge conflicted by this PR.
Changelog
(Deliberately not properly formatting this for the bot, this is a joke.)