-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
*: add aliases for 21 deleted TiDB Binlog docs from dev #18625
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lilin90
added
translation/doing
This PR’s assignee is translating this PR.
v8.4
This PR/issue applies to TiDB v8.4.
labels
Sep 12, 2024
ti-chi-bot
bot
added
the
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
label
Sep 12, 2024
lilin90
changed the title
Add aliases for deleted TiDB Binlog docs from dev
*: add aliases for 21 deleted TiDB Binlog docs from dev
Sep 12, 2024
lilin90
added
the
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
label
Sep 13, 2024
This was referenced Sep 13, 2024
lilin90
added
translation/done
This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR.
and removed
translation/doing
This PR’s assignee is translating this PR.
labels
Sep 14, 2024
hfxsd
approved these changes
Sep 19, 2024
[LGTM Timeline notifier]Timeline:
|
lilin90
removed
the
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
label
Sep 27, 2024
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lilin90 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
lgtm
needs-1-more-lgtm
Indicates a PR needs 1 more LGTM.
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
translation/done
This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR.
v8.4
This PR/issue applies to TiDB v8.4.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
This PR adds aliases for 21 TiDB Binlog document files deleted from the master branch via #18576. This is for the release of v8.4.0.
Note: The content in the
aliases
section comes from that in the files of the master branch. In addition to that, I add the alias for the URL of the current dev version.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 (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?