Skip to content
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 2 commits into from
Dec 31, 2024
Merged

ci(Mergify): enforce linear history #598

merged 2 commits into from
Dec 31, 2024

Conversation

reaver-flomesh
Copy link
Collaborator

Description:

Testing done:

Affected area:

Functional Area
New Functionality [ ]
CI System [ ]
CLI Tool [ ]
Certificate Management [ ]
Control Plane [ ]
Demo [ ]
Documentation [ ]
Egress [ ]
Ingress [ ]
Install [ ]
Networking [ ]
Observability [ ]
Performance [ ]
SMI Policy [ ]
Security [ ]
Sidecar Injection [ ]
Tests [ ]
Upgrade [ ]
Other [ ]

Please answer the following questions with yes/no.

  1. Does this change contain code from or inspired by another project?

    • Did you notify the maintainers and provide attribution?
  2. Is this a breaking change?

  3. Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)?

@reaver-flomesh 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 reaver-flomesh added this to the v1.5.0 milestone Dec 31, 2024
@reaver-flomesh reaver-flomesh self-assigned this Dec 31, 2024
@mergify mergify bot added the auto-squash label Dec 31, 2024
Copy link
Contributor

mergify bot commented Dec 31, 2024

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(\[wip\]|\[backport\]|\[cherry-pick\])?( )?(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 Enforce verified commits

Wonderful, this rule succeeded.

Make sure that we have verified commits

  • #commits-unverified = 0

🟢 Enforce linear history

Wonderful, this rule succeeded.

Make sure that we have a linear history, no merge commits are allowed

  • linear-history

@reaver-flomesh
Copy link
Collaborator Author

/lgtm

@reaver-flomesh reaver-flomesh merged commit 3ead008 into main Dec 31, 2024
27 checks passed
@reaver-flomesh reaver-flomesh deleted the ci/mergify-config branch December 31, 2024 03:43
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]>
@github-actions github-actions bot added the ok-to-merge The PR can be merged label Dec 31, 2024
@github-actions github-actions bot added the squash Auto squash and merge the PR label Dec 31, 2024
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants