chore: update repositories for workflows re staging, hotfix, communit…#1988
Merged
Conversation
…y; cleanup of not working workflows.
Reviewer's guide (collapsed on small PRs)Reviewer's GuideExpands GitHub Actions workflow triggers to include staging, hotfix, and community branch patterns while removing several unused issue-related workflows. Flow diagram for event routing to updated workflows and branchesflowchart TD
Start([Repository event])
EventType{Event type}
BranchCheck{Branch matches
configured patterns?}
Start --> EventType
EventType -->|push| PushBranch{Push branch}
EventType -->|pull_request| PRBranch{PR target branch}
EventType -->|workflow_dispatch| ManualDispatch
%% Push handling
PushBranch -->|main, develop,
experimental,
staging/*,
hotfix/*,
community/*/develop,
community/*/staging/*| MP_DS_CI[Run maven-project,
container-images,
dependency-submission
as configured]
PushBranch -->|other| NoWorkflowPush[No workflow triggered
by this PR change]
%% PR handling
PRBranch -->|main, develop,
experimental,
staging/*,
hotfix/*| CI_PR[Run container-images
pull_request]
PRBranch -->|develop, experimental,
main, staging/*,
hotfix/*,
community/*/develop,
community/*/staging| DR_PR[Run dependency-review]
PRBranch -->|other| NoWorkflowPR[No workflow triggered
by this PR change]
%% Manual dispatch
ManualDispatch --> ContainerImagesDispatch[Run container-images
with workflow_dispatch]
MP_DS_CI --> End([Workflows run])
NoWorkflowPush --> End
CI_PR --> End
DR_PR --> End
NoWorkflowPR --> End
ContainerImagesDispatch --> End
%% Removed workflows
Removed[issue-lifecycle-manager,
notify-issue-reporter,
summary workflows
removed]
Start -.no longer routed.-> Removed
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. Scanned Files
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
Removes several non-working GitHub workflows and updates CI workflow branch filters to include staging/hotfix/community branch patterns.
Changes:
- Deleted issue summary / issue lifecycle / reporter notification workflows.
- Expanded branch filters in CI workflows to run on
staging/*,hotfix/*, and somecommunity/*/...branches. - Updated container image workflow triggers to include
staging/*andhotfix/*.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/summary.yml | Removes the “summarize new issues” workflow. |
| .github/workflows/notify-issue-reporter.yml | Removes PR-merge notification workflow for issue reporters. |
| .github/workflows/issue-lifecycle-manager.yml | Removes issue lifecycle automation workflow (labels/auto-close behaviors). |
| .github/workflows/maven-project.yml | Extends PR branch filters to include staging/hotfix/community patterns. |
| .github/workflows/dependency-submission.yml | Extends push branch filters to include staging/hotfix/community patterns. |
| .github/workflows/dependency-review.yml | Extends PR branch filters to include staging/hotfix/community patterns. |
| .github/workflows/container-images.yml | Extends push/PR branch filters to include staging/hotfix patterns. |
|
Caution Review failedThe pull request is closed. Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. 📝 WalkthroughWalkthroughThis PR expands branch trigger patterns for multiple CI workflows and removes three GitHub Actions workflows that automated issue/PR notifications, verification, and AI summarization. Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 1 issue, and left some high level feedback:
- The branch patterns for community staging branches are inconsistent across workflows (e.g.,
community/*/staging/*inmaven-project.ymlvscommunity/*/stagingindependency-submission.ymlanddependency-review.yml); consider aligning these so they target the same set of branches. - If community branches are expected to build container images as well, consider extending
container-images.ymltriggers to include the samecommunity/*/developandcommunity/*/stagingpatterns used in the other workflows for consistency with the new branch strategy.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The branch patterns for community staging branches are inconsistent across workflows (e.g., `community/*/staging/*` in `maven-project.yml` vs `community/*/staging` in `dependency-submission.yml` and `dependency-review.yml`); consider aligning these so they target the same set of branches.
- If community branches are expected to build container images as well, consider extending `container-images.yml` triggers to include the same `community/*/develop` and `community/*/staging` patterns used in the other workflows for consistency with the new branch strategy.
## Individual Comments
### Comment 1
<location> `.github/workflows/maven-project.yml:53` </location>
<code_context>
+ - staging/*
+ - hotfix/*
+ - community/*/develop
+ - community/*/staging/*
+
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Align `community/*/staging` vs `community/*/staging/*` branch patterns across workflows.
This workflow uses `community/*/staging/*`, while `dependency-submission.yml` and `dependency-review.yml` use `community/*/staging` (no trailing `/*`). If the goal is to run on all `community/*/staging/*` branches (e.g. `community/foo/staging/bar`), those two workflows may not trigger for some branches. Please standardize the pattern across workflows to match the intended naming convention.
Suggested implementation:
```
- main
- develop
- experimental
- staging/*
- hotfix/*
- community/*/develop
- community/*/staging
```
To fully implement the suggestion, verify and, if needed, adjust `.github/workflows/dependency-submission.yml` and `.github/workflows/dependency-review.yml` so they use the same `community/*/staging` branch pattern (or, if the intended convention is `community/*/staging/*`, then change this workflow accordingly instead).
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @.github/workflows/maven-project.yml:
- Around line 50-54: Update the branch pattern entries to be consistent: replace
the inconsistent "community/*/staging/*" pattern with "community/*/staging" so
it matches the other workflows, and remove the trailing whitespace after
"hotfix/*" to eliminate stray whitespace; target the branch pattern list entries
that currently contain "staging/*", "community/*/staging/*", and "hotfix/*" to
make these exact textual fixes.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or 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
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.
…y; cleanup of not working workflows.
Summary by Sourcery
Extend CI workflow triggers to cover staging, hotfix, and community branch patterns and remove obsolete issue-related workflows.
CI:
Summary by cubic
Expanded CI workflow coverage to include staging, hotfix, and community branches, ensuring builds and dependency checks run under the new branch strategy. Removed non-working issue automation and summary workflows to reduce noise.
Written for commit b867c27. Summary will update on new commits.
Summary by CodeRabbit
Chores
Revert
✏️ Tip: You can customize this high-level summary in your review settings.