Automating syncing with GitHub Actions (Final Testing going on for Java Track, Open to More Tracks)

Exercism
21

I’d prefer PRs for the docs, filepaths and metadata.

For those interested, the Github action is in PR#2950 in the Java track.

@jagdishdrp with raising the issues for tests, would it update or close the issue it previously raised (if it has not been closed by the next run)?

2 Likes
22

I’ve pushed a commit with the necessary changes, the workflow will now avoid creating duplicate issues. If an issue already exists, it will simply update the existing one instead of opening a new one.

Thanks for bringing it up!

2 Likes
23

I’d also like to have such an Exercism wide GHA, but would prefer having an allow- or deny-list of exercises to sync.

PHP track has it’s own script for sync’ing, reading the list of exercises to sync from a file. This allows us to have appr. 50% of the exercises to sync automatically while the rest is still outdated too much for configlet sync.

24

Nice work, @jagdishdrp!

I think it’s fine to have this Exercism-wide, but I’d like to have an opt-out (as in a do not install) for any tracks that don’t need/don’t want this.

Python is fine for now with a combination of our existing scripts and manually syncing. I do it often enough that I (usually) have very few issues.

3 Likes