ci: dump after merge instead of per PR; full validation on push only - #353
Merged
Merged
Conversation
dump-develop regenerates site/public from the pinned TechEngine after data lands on develop, restricted to the collections the push can affect, and commits it back. Data PRs therefore no longer need a dump commit, which was the 33 minute step every rebase invalidated. PRs keep only the scoped engine validation; the full bundled self-validate runs on pushes. Refs #350
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 9 of #350.
dump-develop.yml: on push to develop touchingdata/**, run the pinned TechEngineapp.dump --changed-since <before>and commitsite/publicback to develop (rebase-retry). Its commit only touchessite/public, so the path filter prevents a loop. Falls back to a full dump if the pinned engine predates--changed-since. Manual run:workflow_dispatchwithfull.validate-data.yml: bundled fullself-validateruns on pushes only; PRs rely on the scoped engine validation.dump_checkonly compares when the dump is touched).github-actions[bot]to develop must be allowed by branch protection. If it is refused, the job fails loudly (no silent drift) and the dump can still be run with the old procedure.Closes #297