[BACKPORT] ci: adjust the regex of validating PR title (#479) #480
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
* ci: adjust the regex of validating PR title Signed-off-by: Lin Yang <[email protected]> * docs: update comment of invalid PR title Signed-off-by: Lin Yang <[email protected]> --------- Signed-off-by: Lin Yang <[email protected]>
reaver-flomesh
added
enhancement
reaver-flomesh
requested review from
cybwan,
addozhang,
naqvis and
caishu97
as code owners
github-actions
bot
added
the
title needs formatting
🚨 PR Title Needs FormattingThe title of this PR needs to be formatted correctly.
For more details, please refer to the Conventional Commits Specification |
reaver-flomesh
removed
the
title needs formatting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ci: adjust the regex of validating PR title
docs: update comment of invalid PR title
Description:
Testing done:
Affected area:
Please answer the following questions with yes/no.
Does this change contain code from or inspired by another project?
Is this a breaking change?
Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)?