ci: allow notification of upstream changes #1013
Conversation
wattanx
force-pushed
the
ci/needs-port-upstream
branch
from
472f78d
to
9a3fa44
Compare
|
@danielroe |
| id: set-result | ||
| with: | ||
| script: | | ||
| const { data } = await github.request('GET /repos/{owner}/{repo}/commits/{commit_sha}/pulls', { |
There was a problem hiding this comment.
do you think we could instead pass the pull sha via repository_dispatch action rather than performing another request? (I wonder if two PRs merged quickly might end up creating the same issue.)
There was a problem hiding this comment.
I think it's possible by changing the trigger from push to pull_request.
I'll give it a try.
There was a problem hiding this comment.
By using pull_request as the trigger, I was able to obtain the html_url, so I tried passing it directly. What do you think?
https://github.com/wattanx/repository-dispatch-owner/blob/main/.github/workflows/dispatch-update-file.yml#L22
🔗 Linked issue
❓ Type of change
📚 Description
The composables in nuxt/bridge are ported from nuxt 3.
So, if there are changes in nuxt 3, we need to follow the changes.
This PR notifies this repository of any modifications on the nuxt 3 side to reduce porting leaks.
Examples of Notification:
wattanx/repository-dispatch-target#4
The notifier prepares the following workflow:
https://github.com/wattanx/repository-dispatch-owner/blob/main/.github/workflows/dispatch-update-file.yml
📝 Checklist