Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/workflows/cloud-release-docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -48,3 +48,16 @@ jobs:
commit_user_name: l5io
commit_user_email: ci@layer5.io
commit_author: ${{ github.actor }} <${{ github.actor }}@users.noreply.github.com>
# The checkout above is pinned to the SHA this run was dispatched at,
# so anything landing on master while the job runs - notably the
# cross-repo chart publisher in layer5io/meshery-cloud - leaves this
# job pushing from a stale base and the release notes are lost with
# the rejected push. Replay this commit on the current tip first.
# Safe to rebase: this job only touches build/meshery-cloud.version
# and its own release-notes page, which nothing else writes.
# The action passes its identity per-command and never configures it,
# so the rebase has to be handed the same one or it picks up whatever
# the runner guesses.
before_push_hook: >-
git -c user.name="$INPUT_COMMIT_USER_NAME" -c user.email="$INPUT_COMMIT_USER_EMAIL"
pull --rebase --autostash origin "$INPUT_BRANCH"
Comment thread
coderabbitai[bot] marked this conversation as resolved.
11 changes: 11 additions & 0 deletions .github/workflows/meshery-extension-release-docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -48,3 +48,14 @@ jobs:
commit_user_name: l5io
commit_user_email: ci@layer5.io
commit_author: ${{ github.actor }} <${{ github.actor }}@users.noreply.github.com>
# Same stale-base hazard as cloud-release-docs.yml: the checkout is
# pinned to the dispatch SHA, so any commit landing on master during
# the run makes this push non-fast-forward and discards the notes.
# Safe to rebase: this job only touches build/meshery-extensions.version
# and its own release-notes page, which nothing else writes.
# The action passes its identity per-command and never configures it,
# so the rebase has to be handed the same one or it picks up whatever
# the runner guesses.
before_push_hook: >-
git -c user.name="$INPUT_COMMIT_USER_NAME" -c user.email="$INPUT_COMMIT_USER_EMAIL"
pull --rebase --autostash origin "$INPUT_BRANCH"
Loading