-
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
tidb-functions: add info about special start_key/end_key values #16136
tidb-functions: add info about special start_key/end_key values #16136
Conversation
add translation the document of tidb-functions.md from the pull request of pingcap#6728
tidb-functions: add info about special start_key/end_key values
…#6728-tidb-functions
/translation from-docs |
@RobertCheng-956 Please update the content according to comments. |
OK. There should be a space before and after inline cold wrapped by backticks? |
Co-authored-by: Lilian Lee <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
It's one rule in the PingCAP Style Guide. See 4.1.1 空白的使用 in https://github.com/pingcap/docs-cn/blob/master/resources/pingcap-style-guide-zh.pdf. |
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
[LGTM Timeline notifier]Timeline:
|
/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 |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Got it. Thank you. |
What is changed, added or deleted? (Required)
translate-docs-pr#6728
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?