Misc github actions improve#1253
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
There was a problem hiding this comment.
Pull request overview
This PR updates GitHub Actions workflows to better support release-branch pull requests and introduces a workflow-level gating pattern (via paths-filter) to avoid running E2E jobs when unrelated files change, while still producing a passing check.
Changes:
- Extend multiple CI workflows to trigger on pull requests targeting
release-*branches. - Update the E2E workflow to always run a lightweight “changes” job and conditionally run the E2E matrix only when relevant files changed.
- Minor YAML normalization (quoting / formatting) across several workflows.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/python-tests.yml | Adds release-branch PR triggering for Python tests. |
| .github/workflows/python-lint.yml | Adds release-branch PR triggering for Python lint. |
| .github/workflows/go-tests.yml | Adds release-branch PR triggering for Go unit tests; minor quoting changes. |
| .github/workflows/go-check.yml | Adds release-branch PR triggering for Go checks. |
| .github/workflows/e2e-tests.yml | Introduces paths-filter gating to skip E2E matrix when irrelevant, while keeping a passing workflow run. |
| .github/workflows/docs-tests.yml | Adds release-branch PR triggering for docs tests; minor quoting changes. |
| .github/workflows/codespell.yaml | Adds release-branch PR triggering for codespell. |
| .github/workflows/build-push-release.yml | Adds release-branch PR triggering; minor formatting/quoting changes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| pull_request: | ||
| branches: | ||
| - main | ||
| - "release-**" | ||
| paths: |
| pull_request: | ||
| branches: | ||
| - main | ||
| - "release-**" | ||
| paths-ignore: |
| pull_request: | ||
| branches: | ||
| - main | ||
| paths: | ||
| - "pkg/**" | ||
| - "cmd/**" | ||
| - "test/**" | ||
| - "config/**" | ||
| - "charts/**" | ||
| - "docker/**" | ||
| - "hack/**" | ||
| - "go.mod" | ||
| - "go.sum" | ||
| - "Makefile" | ||
| - ".github/workflows/e2e-tests.yml" | ||
| - "release-**" | ||
|
|
abf7873 to
10e160d
Compare
| paths: | ||
| - '**.go' | ||
| - "**.go" | ||
| - "pkg/**" | ||
| - "cmd/**" |
| paths: | ||
| - '**.go' | ||
| - "**.go" | ||
| - "pkg/**" | ||
| - "cmd/**" |
10e160d to
97e022e
Compare
| predicate-quantifier: every | ||
| filters: | | ||
| go_check: | ||
| - "**" | ||
| - "!**.md" | ||
| - "!**.svg" | ||
| - "!**.png" | ||
| - "!docs/**" | ||
| - "!.github/**" | ||
|
|
| with: | ||
| predicate-quantifier: every | ||
| filters: | | ||
| go_check: |
There was a problem hiding this comment.
If I modify both the Go file and these files, will this workflow be triggered?
There was a problem hiding this comment.
either one matches, it will be triggered
|
/hold Lets do this after release-1.0 |
6b3c5a3 to
de2ebf6
Compare
| with: | ||
| predicate-quantifier: every | ||
| filters: | |
| build_images: | ||
| needs: setup | ||
| runs-on: ${{ matrix.os }} | ||
| permissions: | ||
| contents: read | ||
| packages: write |
Signed-off-by: Zhonghu Xu <xuzhonghu@huawei.com>
Signed-off-by: Zhonghu Xu <xuzhonghu@huawei.com>
Signed-off-by: Zhonghu Xu <xuzhonghu@huawei.com>
Signed-off-by: Zhonghu Xu <xuzhonghu@huawei.com>
Signed-off-by: Zhonghu Xu <xuzhonghu@huawei.com>
de2ebf6 to
7073259
Compare
|
@LiZhenCheng9527 Ready to review |
|
Hi I also have a small question, currently if any user do /retest even if it's not the member in the org the e2e cycles restarted so I just want to know if it's intentional or not |
What type of PR is this?
/kind test
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: