Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#1282] bugfix(CI) Automatically trigger CI for auto-cherry-pick workflow #1342

Conversation

jerryshao
Copy link
Contributor

Based on the document of github-cherry-pick-action, add token input to change the default token that the auto-cherry-pick workflow used.

Warning

Need to add a PAT to the organization with the name BOT_TOKEN.

What changes were proposed in this pull request?

Automatically trigger CI for auto-cherry-pick workflow with a customized token, instead of the default GITHUB_TOKEN, which is prohibited from triggering another workflow.

Why are the changes needed?

Fix: #1282

Does this PR introduce any user-facing change?

No user-facing change, but we should add a PAT to the organization with the name BOT_TOKEN.

How was this patch tested?

N/A

…flow (#1337)

Based on the document of
[`github-cherry-pick-action`](https://github.com/marketplace/actions/github-cherry-pick-action#action-inputs),
add token input to change the default token that the auto-cherry-pick
workflow used.

> [!WARNING]  
> Need to add a PAT to the organization with the name `BOT_TOKEN`.

### What changes were proposed in this pull request?

Automatically trigger CI for auto-cherry-pick workflow with a customized
token, instead of the default `GITHUB_TOKEN`, which is prohibited from
triggering another workflow.

### Why are the changes needed?

Fix: #1282 

### Does this PR introduce _any_ user-facing change?

No user-facing change, but we should add a PAT to the organization with
the name `BOT_TOKEN`.

### How was this patch tested?

N/A

Signed-off-by: Bo-Wei Chen(BWbwchen) <tim.chenbw@gmail.com>
@jerryshao jerryshao added cherry-pick need backport Issues that need to backport to another branch labels Jan 5, 2024
Copy link

github-actions bot commented Jan 5, 2024

Code Coverage Report

Overall Project 66.02% 🟢

There is no coverage information present for the Files changed

@qqqttt123 qqqttt123 merged commit 3fda6b0 into branch-0.3 Jan 5, 2024
4 checks passed
@qqqttt123 qqqttt123 deleted the cherry-pick-branch-0.3-18882464aa3d1981f6b3fe9013e81f2a2198b024 branch January 5, 2024 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick need backport Issues that need to backport to another branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants