Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cross repository actions / workflows => update the pages repo on release #1093

Open
tobiu opened this issue Aug 17, 2020 · 0 comments
Open

cross repository actions / workflows => update the pages repo on release #1093

tobiu opened this issue Aug 17, 2020 · 0 comments

Comments

@tobiu
Copy link
Collaborator

@tobiu tobiu commented Aug 17, 2020

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_dispatch or 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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.