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

[backport] ci: slash commands workflow (#599) #600

Merged
merged 1 commit 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)?


    This is an automatic backport of pull request ci: slash commands workflow #599 done by Mergify.

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 reaver-flomesh force-pushed the mergify/bp/release/v1.4/pr-599 branch from 5e0780d to d18128f Compare December 31, 2024 03:36
@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 and removed auto-squash labels Dec 31, 2024
@reaver-flomesh reaver-flomesh added this to the v1.4.17 milestone Dec 31, 2024
@reaver-flomesh
Copy link
Collaborator Author

/lgtm

@github-actions github-actions bot added ok-to-merge The PR can be merged squash Auto squash and merge the PR labels Dec 31, 2024
@reaver-flomesh reaver-flomesh enabled auto-merge (squash) December 31, 2024 05:38
@reaver-flomesh reaver-flomesh force-pushed the mergify/bp/release/v1.4/pr-599 branch from d18128f to 1042294 Compare December 31, 2024 05:40
Copy link
Contributor

mergify bot commented Dec 31, 2024

❗❗❗
All commits in this PR must be signed off.
Please sign all commits by:

git rebase HEAD~1 --signoff
git push --force-with-lease origin mergify/bp/release/v1.4/pr-599

Signed-off-by: Lin Yang <[email protected]>
(cherry picked from commit b26a6fb)
Signed-off-by: Lin Yang <[email protected]>
@reaver-flomesh reaver-flomesh force-pushed the mergify/bp/release/v1.4/pr-599 branch from 1042294 to 7b7d6c3 Compare December 31, 2024 05:42
@mergify mergify bot merged commit 9a19c3e into release/v1.4 Dec 31, 2024
29 checks passed
@mergify mergify bot deleted the mergify/bp/release/v1.4/pr-599 branch December 31, 2024 07:04
reaver-flomesh added a commit to cybwan/fsm that referenced this pull request Dec 31, 2024
ci: slash commands workflow (flomesh-io#599)


(cherry picked from commit b26a6fb)

Signed-off-by: Lin Yang <[email protected]>
reaver-flomesh added a commit to cybwan/fsm that referenced this pull request Dec 31, 2024
ci: slash commands workflow (flomesh-io#599)

(cherry picked from commit b26a6fb)

Signed-off-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 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