Create run-configlet-sync.yml #561
Open
+10
−0
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
lpil
reviewed
Jul 1, 2025
|
|
||
| jobs: | ||
| call-gha-workflow: | ||
| uses: exercism/github-actions/.github/workflows/configlet-sync.yml@main |
Member
There was a problem hiding this comment.
If this is added shouldn't we pin to a specific sha? As we do with all other actions.
Member
Author
There was a problem hiding this comment.
The gha-best-practices documentation states:
When using other actions, pin them to a commit (via their SHA), not to a branch or tag.
However, since we're using an internal workflow from the github-actions repo, we don’t need to pin it to a specific SHA; referencing it by branch is appropriate in this case.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
🛠️ Automating Configlet Sync
This PR introduces a workflow that automates
configlet syncfor test (only an issue is raised), docs, metadata, and filepaths. There are two jobs in the main workflow; we can skip either one of them. Let me know how you'd like to set it up!⏱️ The workflow is currently scheduled to run on the 15th of every month via cron.
Let me know if you'd prefer a different schedule (e.g., weekly, the 1st of each month, etc.).
This setup is already being used across multiple tracks!.
For more context and discussion, see:
🔗 https://forum.exercism.org/t/automating-syncing-with-github-actions-final-testing-going-on-for-java-track-open-to-more-tracks/17807