chore: sync template to v1.6.3, preserving CI efficiency customisations from #22#31
Merged
Merged
Conversation
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.
Summary
Intended to supersede pull request #28, which conflicts with
mainbecause a separate, already-merged pull request (#22, "chore: CI efficiency improvements") customised the same workflow files the template sync touches.This branch was built by running the sync script fresh against current
main, so it brings in the rest of the v1.6.3 template while preserving all three deliberate customisations from #22:In practice these three customisations already match the current master template content (they appear to have been backported upstream since #22 merged), so after the sync ran, only the removal of the re-added Playwright workflow needed to be manually reapplied. The other template changes (updated pinned action SHAs, refreshed
.github/accessibility-tools/package-lock.json,.claude/template-versionbumped to 1.6.3) came through unchanged from the sync.This should supersede #28 once Sonja and Tim confirm; #28 has been left open with a comment pointing here rather than closed, since closing an existing pull request isn't a pre-approved action for this branch of work.
No test changes were needed since this is a CI/template configuration sync with no application code change.