scripts/verify-links: update link check error messages#2292
Merged
Conversation
yikeke
added
needs-cherry-pick-3.1
translation/done
yikeke
commented
Feb 24, 2020
1 task
This was referenced Feb 24, 2020
Contributor
|
cherry pick to release-2.1 in PR #2293 |
1 task
Contributor
|
cherry pick to release-3.0 in PR #2294 |
Contributor
|
cherry pick to release-3.1 in PR #2295 |
yikeke
added a commit
that referenced
this pull request
Feb 25, 2020
yikeke
added a commit
that referenced
this pull request
Feb 25, 2020
yikeke
added a commit
that referenced
this pull request
Feb 25, 2020
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
update error messages in link check CI report
What is the related PR or file link(s)?
Important Notice:
If your changes apply to multiple TiDB documentation versions, to trigger the bot to cherry-pick this PR to other release branches, make sure you add labels such as: