Potential GitHub automation workflow/script improvements #384
Labels
Agenda+Community Group
To discuss in the next workstream summary meeting (usually the last teleconference of the month)
enhancement
New feature or request
tests
About assistive technology tests
The GitHub Action, triggered by pushing to a PR branch, currently executes the create-all-tests and review-tests scripts. These cause all assets to be regenerated for all patterns present in the
tests
directory, even though a test developer will typically only be working on one pattern at a time.As the number of patterns in the
tests
directory increases, so will the running time of the scripts and workflow. The current approach also increases the likelihood of merge conflicts (e.g. like those seen in PR #330), because files are updated which have no relation to the test pattern under development.Additional Observations
tests.csv
.Suggested Enhancements
In priority order:
git push
followed bygit pull
dance.The text was updated successfully, but these errors were encountered: