-
Notifications
You must be signed in to change notification settings - Fork 709
.github: add a yml to auto assign new PRs and issues to sig project #2598
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
Conversation
lilin90
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ingcap#2598) * .github: add a yml to auto assign new PRs and issues to sig project * assign translation/welcome pr to related column * update actions for 5 columns * add unlabeled as a trigger
|
cherry pick to release-2.1 in PR #2606 |
|
cherry pick to release-3.0 failed |
|
cherry pick to release-3.1 failed |
…ingcap#2598) * .github: add a yml to auto assign new PRs and issues to sig project * assign translation/welcome pr to related column * update actions for 5 columns * add unlabeled as a trigger
|
cherry pick to release-4.0 in PR #2607 |
|
/run-cherry-picker |
…ingcap#2598) * .github: add a yml to auto assign new PRs and issues to sig project * assign translation/welcome pr to related column * update actions for 5 columns * add unlabeled as a trigger
|
cherry pick to release-3.0 in PR #2608 |
…ingcap#2598) * .github: add a yml to auto assign new PRs and issues to sig project * assign translation/welcome pr to related column * update actions for 5 columns * add unlabeled as a trigger
|
cherry pick to release-3.1 in PR #2609 |
|
This yml does not work as expected. I created a new PR: #2605 |
What is changed, added or deleted? (Required)
Automate the Docs SIG project process:
PR: In ProgressIssue: BacklogPR: DoneIssue: Resolvedtranslation/welcomelabel toTranslation/WelcomeWhich TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?