Create run-configlet-sync.yml

[jagdish-15]

🛠️ Automating Configlet Sync

This PR introduces a workflow that automates configlet sync for 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

[github-actions]

Hello. Thanks for opening a PR on Exercism 🙂

We ask that all changes to Exercism are discussed on our Community Forum before being opened on GitHub. To enforce this, we automatically close all PRs that are submitted. That doesn't mean your PR is rejected but that we want the initial discussion about it to happen on our forum where a wide range of key contributors across the Exercism ecosystem can weigh in.

You can use this link to copy this into a new topic on the forum. If we decide the PR is appropriate, we'll reopen it and continue with it, so please don't delete your local branch.

If you're interested in learning more about this auto-responder, please read this blog post.

---

Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

[senekor]

Sounds cool, gonna have a closer look later and probably merge.

[senekor]

Just for reference, we currently have a system where we pin problem-specifications to a specific commit so we can reliably test if the tests checked into the repo are the same as the ones produced by the test generator. We should probably get rid of that, adopting this PR new action is a different, incompatible approach.

[jagdish-15]

Hey @senekor, I don’t have much experience with that setup myself!

Would you mind adding a quick comment about this on the forum discussion? It might help others understand the implications of adopting the new workflow, especially if they’re relying on that pinning system.

[senekor]

The pinning system is a custom approach here on the Rust track, so no need to post on the forum. I just wanted to document that thought here in case someone in the future (or me, being forgetful) stumbles here and wonders how the two systems are supposed to interact.