mirror of
https://gitee.com/openharmony/third_party_littlefs
synced 2024-11-23 14:59:50 +00:00
c9110617b3
This helps an outstanding maintainer annoyance: updating dependencies to bring in new versions on each littlefs release. But instead of adding a bunch of scripts to the tail end of the release workflow, the post-release script just triggers a single "repository_dispatch" event in the newly created littlefs.post-release repo. From there any number of post-release workflows can be run. This indirection should let the post-release scripts move much quicker than littlefs itself, which helps offset how fragile these sort of scripts are. --- Also finished cleaning up the workflows now that they are mostly working.
27 lines
914 B
YAML
27 lines
914 B
YAML
name: post-release
|
|
on:
|
|
release:
|
|
branches: [master]
|
|
types: [released]
|
|
|
|
jobs:
|
|
post-release:
|
|
runs-on: ubuntu-18.04
|
|
steps:
|
|
# trigger post-release in dependency repo, this indirection allows the
|
|
# dependency repo to be updated often without affecting this repo. At
|
|
# the time of this comment, the dependency repo is responsible for
|
|
# creating PRs for other dependent repos post-release.
|
|
- name: trigger-post-release
|
|
continue-on-error: true
|
|
run: |
|
|
curl -sS -X POST -H "authorization: token ${{secrets.BOT_TOKEN}}" \
|
|
"$GITHUB_API_URL/repos/${{secrets.POST_RELEASE_REPO}}/dispatches" \
|
|
-d "$(jq -n '{
|
|
event_type: "post-release",
|
|
client_payload: {
|
|
repo: env.GITHUB_REPOSITORY,
|
|
version: "${{github.event.release.tag_name}}"}}' \
|
|
| tee /dev/stderr)"
|
|
|