Automatic Releases Workflow

[Stefterv]

Added a workflow to be able to trigger the fetchReleases script and create a pull request on the repo.

This workflow can be triggered manually, and then we can decide if we want to automatically also update the content/download/selected.json or if that would have to be done manually

[netlify]

✅ Deploy Preview for java-processing-faf822 ready!

Name	Link
🔨 Latest commit	3f8e87e
🔍 Latest deploy log	https://app.netlify.com/sites/java-processing-faf822/deploys/675b12376442f5000898dd9d
😎 Deploy Preview	https://deploy-preview-589--java-processing-faf822.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Stefterv]

Seems like we need to setup a Personal Access Token instead as the defined Github token can only read the current repository

[Stefterv]

One thing I dislike about the current system is that we have duplicate data, the original repo maintains its own state for releases and the website is not dynamically updating based on that.

One other approach would be to remove the releases content from this repo altogether, download the data on every build. And make the processing4 repo trigger a web hook on netlify.

[SableRaf]

Seems like we need to setup a Personal Access Token instead as the defined Github token can only read the current repository

Which specific repository permissions does this token need?

[SableRaf]

One thing I dislike about the current system is that we have duplicate data, the original repo maintains its own state for releases and the website is not dynamically updating based on that.

Agreed!

One other approach would be to remove the releases content from this repo altogether, download the data on every build. And make the processing4 repo trigger a web hook on netlify.

That sounds reasonable and would support the goal to adopt a more pull-based data flow across the Processing infra.