-
Notifications
You must be signed in to change notification settings - Fork 10
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
ci(Mergify): enforce linear history #598
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
reaver-flomesh
added
area/CI
Task/Issue related to CI
change/github-actions
Pull requests that update GitHub Actions code
kind/enhancement
New feature or request
priority/P1
P1 priority
size/XS
1 day
backport/v1.4
Backport PR to release/v1.4 branch
labels
Dec 31, 2024
reaver-flomesh
requested review from
cybwan,
naqvis,
caishu97 and
i0r3k
as code owners
December 31, 2024 02:53
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 Enforce verified commitsWonderful, this rule succeeded.Make sure that we have verified commits
🟢 Enforce linear historyWonderful, this rule succeeded.Make sure that we have a linear history, no merge commits are allowed
|
reaver-flomesh
force-pushed
the
ci/mergify-config
branch
from
December 31, 2024 03:33
9fed09b
to
9c3823e
Compare
Signed-off-by: Lin Yang <[email protected]>
Signed-off-by: Lin Yang <[email protected]>
reaver-flomesh
force-pushed
the
ci/mergify-config
branch
from
December 31, 2024 03:35
9c3823e
to
7a55c1e
Compare
i0r3k
approved these changes
Dec 31, 2024
/lgtm |
mergify bot
pushed a commit
that referenced
this pull request
Dec 31, 2024
* ci(Mergify): enforce linear history Signed-off-by: Lin Yang <[email protected]> * fix: backport labels Signed-off-by: Lin Yang <[email protected]> --------- Signed-off-by: Lin Yang <[email protected]> (cherry picked from commit 3ead008)
reaver-flomesh
added a commit
that referenced
this pull request
Dec 31, 2024
* ci(Mergify): enforce linear history Signed-off-by: Lin Yang <[email protected]> * fix: backport labels Signed-off-by: Lin Yang <[email protected]> --------- Signed-off-by: Lin Yang <[email protected]> (cherry picked from commit 3ead008) Signed-off-by: Lin Yang <[email protected]>
mergify bot
added a commit
that referenced
this pull request
Dec 31, 2024
ci(Mergify): enforce linear history (#598) * ci(Mergify): enforce linear history * fix: backport labels --------- (cherry picked from commit 3ead008) Signed-off-by: Lin Yang <[email protected]> Co-authored-by: Lin Yang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/CI
Task/Issue related to CI
backport/v1.4
Backport PR to release/v1.4 branch
change/github-actions
Pull requests that update GitHub Actions code
kind/enhancement
New feature or request
ok-to-merge
The PR can be merged
priority/P1
P1 priority
size/XS
1 day
squash
Auto squash and merge the PR
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.
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)?