LearnNewsExamplesServices
Frontmatter
id1093
titlecross repository actions / workflows => update the pages repo on release
stateClosed
labels
enhancementhelp wantedgood first issuestale
assignees[]
createdAtAug 17, 2020, 4:40 PM
updatedAtSep 27, 2024, 4:34 AM
githubUrlhttps://github.com/neomjs/neo/issues/1093
authortobiu
commentsCount2
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtSep 27, 2024, 4:34 AM

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

Closed v8.1.0 enhancementhelp wantedgood first issuestale
tobiu
tobiu commented on Aug 17, 2020, 4:40 PM

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

tobiu added the enhancement label on Aug 17, 2020, 4:40 PM
tobiu added the help wanted label on Aug 17, 2020, 4:40 PM
tobiu added the good first issue label on Aug 17, 2020, 4:40 PM