Update some exclamation. #1

vdemeester · 2025-11-25T09:56:27Z

Signed-off-by: Vincent Demeester [email protected]

vdemeester · 2025-11-25T09:57:04Z

/cherry-pick foo-is-bar

vdemeester · 2025-11-25T10:04:18Z

/cherry-pick foo-is-bar

vdemeester · 2025-11-25T10:12:48Z

/cherry-pick foo-is-bar

Signed-off-by: Vincent Demeester <[email protected]>

vdemeester · 2025-11-25T10:17:51Z

/cherry-pick foo-is-bar

vdemeester · 2025-11-25T10:20:08Z

/build

vdemeester · 2025-11-25T10:27:24Z

/cherry-pick foo-is-bar

vdemeester · 2025-11-25T10:27:46Z

/build

vdemeester · 2025-11-25T10:33:30Z

/cherry-pick foo-is-bar

vdemeester · 2025-11-25T10:38:02Z

/cherry-pick foo-is-bar

vdemeester · 2025-11-25T10:41:49Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T10:42:11Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar encountered conflicts or errors.

You'll need to manually cherry-pick this PR.

vdemeester · 2025-11-25T10:47:35Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T10:47:59Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Possible causes:

The PR is not merged yet (cherry-pick requires merged PRs)
Merge conflicts exist between this PR and the target branch
The target branch foo-is-bar does not exist

Next steps:

Check the action logs for detailed error messages
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T10:54:03Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T10:54:28Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Error output:

Possible causes:

The PR is not merged yet (cherry-pick requires merged PRs)
Merge conflicts exist between this PR and the target branch
The target branch foo-is-bar does not exist

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T10:58:02Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T10:58:33Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Error output:

Possible causes:

The PR is not merged yet (cherry-pick requires merged PRs)
Merge conflicts exist between this PR and the target branch
The target branch foo-is-bar does not exist

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T10:59:50Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T11:00:15Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Error output:

Possible causes:

The PR is not merged yet (cherry-pick requires merged PRs)
Merge conflicts exist between this PR and the target branch
The target branch foo-is-bar does not exist

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T11:19:05Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T11:19:25Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
Unknown JSON field: "merged"
Available fields:
  additions
  assignees
  author
  autoMergeRequest
  baseRefName
  baseRefOid
  body
  changedFiles
  closed
  closedAt
  closingIssuesReferences
  comments
  commits
  createdAt
  deletions
  files
  fullDatabaseId
  headRefName
  headRefOid
  headRepository
  headRepositoryOwner
  id
  isCrossRepository
  isDraft
  labels
  latestReviews
  maintainerCanModify
  mergeCommit
  mergeStateStatus
  mergeable
  mergedAt
  mergedBy
  milestone
  number
  potentialMergeCommit
  projectCards
  projectItems
  reactionGroups
  reviewDecision
  reviewRequests
  reviews
  state
  statusCheckRollup
  title
  updatedAt
  url
❌ ERROR: PR #1 is not merged yet. Cherry-pick requires merged PRs.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T11:26:05Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T11:26:26Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
❌ ERROR: PR #1 is not merged yet (state: OPEN). Cherry-pick requires merged PRs.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T11:30:47Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T11:31:09Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
Found merge commit: ff4dfe0161f032e4c7723ab70e9fb57970a37f6d
Fetching target branch: foo-is-bar...
fatal: couldn't find remote ref foo-is-bar
❌ ERROR: Target branch 'foo-is-bar' does not exist or cannot be fetched.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T11:33:25Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T11:33:44Z

❌ Cherry-pick failed!

The automatic cherry-pick to foo-is-bar failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
Found merge commit: ff4dfe0161f032e4c7723ab70e9fb57970a37f6d
Fetching target branch: foo-is-bar...
From https://github.com/shortbrain/workflows-experiments
 * branch            foo-is-bar -> FETCH_HEAD
Creating cherry-pick branch: cherry-pick-1-to-foo-is-bar...
Switched to a new branch 'cherry-pick-1-to-foo-is-bar'
branch 'cherry-pick-1-to-foo-is-bar' set up to track 'origin/foo-is-bar'.
Cherry-picking commit ff4dfe0161f032e4c7723ab70e9fb57970a37f6d...
Committer identity unknown

*** Please tell me who you are.

Run

  git config --global user.email "[email protected]"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident name (for <runner@runnervmg1sw1.uzm4dnevkx0exmdpusqguksr3c.dx.internal.cloudapp.net>) not allowed
❌ ERROR: Cherry-pick failed due to conflicts or other errors.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T11:41:04Z

/cherry-pick foo-is-bar

sbr-bot · 2025-11-25T11:41:26Z

✅ Cherry-pick successful!

A new pull request has been created to cherry-pick this change to foo-is-bar.

Please review and merge the cherry-pick PR.

vdemeester · 2025-11-25T22:38:40Z

/cherry-pick foo-is-bar foo-is-baz

sbr-bot · 2025-11-25T22:39:06Z

❌ Cherry-pick to foo-is-bar failed!

The automatic cherry-pick to foo-is-bar failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
Found merge commit: ff4dfe0161f032e4c7723ab70e9fb57970a37f6d
Fetching target branch: foo-is-bar...
From https://github.com/shortbrain/workflows-experiments
 * branch            foo-is-bar -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-1-to-foo-is-bar...
Switched to a new branch 'cherry-pick-1-to-foo-is-bar'
branch 'cherry-pick-1-to-foo-is-bar' set up to track 'origin/foo-is-bar'.
Cherry-picking commit ff4dfe0161f032e4c7723ab70e9fb57970a37f6d...
The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git cherry-pick --skip'
On branch cherry-pick-1-to-foo-is-bar
Your branch is up to date with 'origin/foo-is-bar'.

You are currently cherry-picking commit ff4dfe0.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

nothing to commit, working tree clean
❌ ERROR: Cherry-pick failed due to conflicts or other errors.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

sbr-bot · 2025-11-25T22:39:08Z

❌ Cherry-pick to foo-is-baz failed!

The automatic cherry-pick to foo-is-baz failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
Found merge commit: ff4dfe0161f032e4c7723ab70e9fb57970a37f6d
Fetching target branch: foo-is-baz...
From https://github.com/shortbrain/workflows-experiments
 * branch            foo-is-baz -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-1-to-foo-is-baz...
Switched to a new branch 'cherry-pick-1-to-foo-is-baz'
branch 'cherry-pick-1-to-foo-is-baz' set up to track 'origin/foo-is-baz'.
Cherry-picking commit ff4dfe0161f032e4c7723ab70e9fb57970a37f6d...
The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git cherry-pick --skip'
On branch cherry-pick-1-to-foo-is-baz
Your branch is up to date with 'origin/foo-is-baz'.

You are currently cherry-picking commit ff4dfe0.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

nothing to commit, working tree clean
❌ ERROR: Cherry-pick failed due to conflicts or other errors.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

sbr-bot · 2025-11-25T22:39:20Z

ℹ️ Cherry-pick to foo-is-bar already exists!

A pull request for this cherry-pick already exists: #2

PR: #2

sbr-bot · 2025-11-25T22:39:20Z

❌ Cherry-pick to foo-is-baz failed!

The automatic cherry-pick to foo-is-baz failed.

Error:

cherry-pick failed due to conflicts or other errors: exit status 1: The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git cherry-pick --skip'
On branch cherry-pick-1-to-foo-is-baz
Your branch is up to date with 'origin/foo-is-baz'.

You are currently cherry-picking commit ff4dfe0.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

nothing to commit, working tree clean

Next steps:

If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester · 2025-11-25T22:42:11Z

/cherry-pick foo-is-bar foo-is-baz

sbr-bot · 2025-11-25T22:42:37Z

👴❌ Cherry-pick to foo-is-baz failed!

The automatic cherry-pick to foo-is-baz failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
Found merge commit: ff4dfe0161f032e4c7723ab70e9fb57970a37f6d
Fetching target branch: foo-is-baz...
From https://github.com/shortbrain/workflows-experiments
 * branch            foo-is-baz -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-1-to-foo-is-baz...
Switched to a new branch 'cherry-pick-1-to-foo-is-baz'
branch 'cherry-pick-1-to-foo-is-baz' set up to track 'origin/foo-is-baz'.
Cherry-picking commit ff4dfe0161f032e4c7723ab70e9fb57970a37f6d...
The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git cherry-pick --skip'
On branch cherry-pick-1-to-foo-is-baz
Your branch is up to date with 'origin/foo-is-baz'.

You are currently cherry-picking commit ff4dfe0.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

nothing to commit, working tree clean
❌ ERROR: Cherry-pick failed due to conflicts or other errors.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

sbr-bot · 2025-11-25T22:42:40Z

👴❌ Cherry-pick to foo-is-bar failed!

The automatic cherry-pick to foo-is-bar failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #1 information...
Found merge commit: ff4dfe0161f032e4c7723ab70e9fb57970a37f6d
Fetching target branch: foo-is-bar...
From https://github.com/shortbrain/workflows-experiments
 * branch            foo-is-bar -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-1-to-foo-is-bar...
Switched to a new branch 'cherry-pick-1-to-foo-is-bar'
branch 'cherry-pick-1-to-foo-is-bar' set up to track 'origin/foo-is-bar'.
Cherry-picking commit ff4dfe0161f032e4c7723ab70e9fb57970a37f6d...
The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git cherry-pick --skip'
On branch cherry-pick-1-to-foo-is-bar
Your branch is up to date with 'origin/foo-is-bar'.

You are currently cherry-picking commit ff4dfe0.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

nothing to commit, working tree clean
❌ ERROR: Cherry-pick failed due to conflicts or other errors.

Next steps:

Check the action logs for complete details
If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

sbr-bot · 2025-11-25T22:42:51Z

ℹ️ Cherry-pick to foo-is-bar already exists!

A pull request for this cherry-pick already exists: #2

PR: #2

sbr-bot · 2025-11-25T22:42:52Z

❌ Cherry-pick to foo-is-baz failed!

The automatic cherry-pick to foo-is-baz failed.

Error:

cherry-pick failed due to conflicts or other errors: exit status 1: The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git cherry-pick --skip'
On branch cherry-pick-1-to-foo-is-baz
Your branch is up to date with 'origin/foo-is-baz'.

You are currently cherry-picking commit ff4dfe0.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

nothing to commit, working tree clean

Next steps:

If the PR is not merged, merge it first and try again
If there are conflicts, you'll need to manually cherry-pick this PR

vdemeester force-pushed the exclamation branch from 597e7e6 to f5115fb Compare November 25, 2025 10:04

Update some exclamation.

3c55466

Signed-off-by: Vincent Demeester <[email protected]>

vdemeester force-pushed the exclamation branch from f5115fb to 3c55466 Compare November 25, 2025 10:17

vdemeester added this pull request to the merge queue Nov 25, 2025

vdemeester removed this pull request from the merge queue due to a manual request Nov 25, 2025

vdemeester merged commit ff4dfe0 into shortbrain:main Nov 25, 2025
3 checks passed

vdemeester mentioned this pull request Nov 25, 2025

feat: Add GitHub Actions cherry-pick slash command tektoncd/pipeline#9172

Merged

8 tasks

sbr-bot mentioned this pull request Nov 25, 2025

Cherry-pick #1 to foo-is-bar #2

Merged

vdemeester deleted the exclamation branch November 25, 2025 21:16

Update some exclamation. #1

Update some exclamation. #1

Uh oh!

Conversation

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

Uh oh!

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!

vdemeester commented Nov 25, 2025

Uh oh!

sbr-bot commented Nov 25, 2025

Uh oh!