Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upcross repository actions / workflows => update the pages repo on release #1093
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I flagged this one as a "good first issue", since it does not require any knowledge of neo.mjs itself.
Also flagged it as "help wanted", since actions & workflows are not a topic i am familiar with (well, setting up the auto npm publish one was easy).
Googled and found some input:
https://github.community/t/triggering-by-other-repository/16163
https://fabianmoronzirfas.me/tech/2019/02/06/cross-repo-github-action-triggering.html
https://github.com/drud/action-cross-commit
What I have in mind:
Once the github action to do an npm publish is done, the neomjs/pages repo needs to trigger an own action.
We could try
on: repository_dispatchor use webhooks (similar to the discord use case to list all events).Once we are able to get an event to start the action inside the pages repo, this one should run:
npm update neo.mjs
npm install
(basically follow the steps of the readme inside the pages repo)
at the end commit & push.
In case someone wants to help out on this one, I can create the required secrets.
Help on this one is definitely appreciated, since it can save me time (so I have more time to push the code base).