-
Notifications
You must be signed in to change notification settings - Fork 701
chore: add a script to create an empty translation PR #13634
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
base: master
Are you sure you want to change the base?
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
if response.status_code == 200: | ||
upstream_sha = response.json().get("object", {}).get("sha") | ||
else: | ||
print("Failed to get the upstream repository branch reference.") |
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.
Is it possible to create a fork here instead of exiting?
|
||
source_title = pr_data["title"] | ||
source_description = pr_data["body"] | ||
source_labels = [label["name"] for label in pr_data.get("labels", []) if "size" not in label["name"] and "translation" not in label["name"] and "status" not in label["name"]] |
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.
first-time-contributor
and contribution
should also be excluded
Co-authored-by: Ran <[email protected]>
First-time contributors' checklist
What is changed, added or deleted? (Required)
This PR adds a script to create an empty translation PR based your specified source language PR.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?