We need to add some CI workflows into the Assets-Master and Assets-Production repositories to validate changes people make to the various files. This might require building some tools (f.e linters) for these files.
- The team has various levels of understanding of the tools and files. Having linters, etc will help level the field and even fill in gaps that have been lost over time.
- Build confidence in the files we have and their ability to be generated.
- Build confidence in proposed changes.
- Help validate and resolve bugs.
- Any tools we build should have good error messages to help point out what is broken and what needs to be fixed. Tools can be built and released via https://github.com/vegastrike/Tools if we need to make custom tools; we can split out any that make sense as their own repository.
[ ] If there is anything needed to be installed then we can add a new image to our CI Build Images so we're kind on resources to Github.
[ ] Linters are needed for the various files we have.
[ ] Use an iterative approach: (i) add only one tool in a PR, (ii) get the basics of a tool together and iterate to improve it through additional PRs, (iii) current files are understood to be good; but its possible they're faulty so this may fix some things as we add it. (iv) document.
We need to add some CI workflows into the Assets-Master and Assets-Production repositories to validate changes people make to the various files. This might require building some tools (f.e linters) for these files.
[ ] If there is anything needed to be installed then we can add a new image to our CI Build Images so we're kind on resources to Github.
[ ] Linters are needed for the various files we have.
[ ] Use an iterative approach: (i) add only one tool in a PR, (ii) get the basics of a tool together and iterate to improve it through additional PRs, (iii) current files are understood to be good; but its possible they're faulty so this may fix some things as we add it. (iv) document.