-
Notifications
You must be signed in to change notification settings - Fork 4
ci: avoid unecessary infra and app runs on irrelevant changes #2296
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
Conversation
📝 WalkthroughWalkthroughThe workflow configuration in Changes
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
.github/workflows/workflow-check-for-changes.yml (2)
73-77
: Scope GitHub workflows detection to the workflows directoryUsing
'.github/**/*'
with multiple exclusions can be fragile. It’s clearer to match only the workflows folder directly:files_yaml: | - github_workflows: - - '.github/**/*' - - '!.github/ISSUE_TEMPLATE/**/*' - - '!.github/CODEOWNERS' - - '!.github/pull_request_template.md' + github_workflows: + - '.github/workflows/**/*'This simplifies the pattern and removes the need for negations.
110-120
: Enhance backend change loggingYou’ve logged the change flags for all categories, but only listed the modified files for
backend
. Consider echoing the modified file lists for other backend-related categories (tests, web_api_client, swagger_schema, etc.) to mirror the infra logging step.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.github/workflows/workflow-check-for-changes.yml
(3 hunks)
🔇 Additional comments (2)
.github/workflows/workflow-check-for-changes.yml (2)
47-48
: Validate inclusion of GitHub workflows in infra and backend detectionThe added
github_workflows_any_modified
flag in bothhasInfraChanges
andhasBackendChanges
means any change to a workflow file will trigger both infrastructure and backend pipelines. Please confirm this behavior aligns with the PR objective of avoiding unnecessary infra/app runs on irrelevant changes.
79-86
: Add logging for infrastructure and workflow file changesThe new log step prints both the boolean flags and the lists of modified infra and workflow files, improving visibility into what’s driving pipeline decisions.
Description
Minor changes like this one: Altinn/dialogporten-frontend#2146 shouldn't trigger a full run of infra and app deployments.
Also removed slacknotifier as it's no longer in use
Related Issue(s)
Verification
Documentation
docs
-directory, Altinnpedia or a separate linked PR in altinn-studio-docs., if applicable)