-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
☁️ Server workflows run only when server files have changed #4348
☁️ Server workflows run only when server files have changed #4348
Conversation
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Warning Rate limit exceeded@MikesGlitch has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 14 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughThe pull request includes modifications to the GitHub Actions workflow for building the Edge Docker image, specifically updating the Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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
CodeRabbit Configuration File (
|
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: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
upcoming-release-notes/4348.md
is excluded by!**/*.md
📒 Files selected for processing (3)
.github/workflows/docker-edge.yml
(1 hunks)packages/sync-server/src/app-simplefin/app-simplefin.js
(1 hunks)packages/sync-server/src/util/middlewares.js
(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- packages/sync-server/src/app-simplefin/app-simplefin.js
⏰ Context from checks skipped due to timeout of 90000ms (5)
- GitHub Check: Functional
- GitHub Check: Visual regression
- GitHub Check: build (macos-latest)
- GitHub Check: build (windows-latest)
- GitHub Check: build (ubuntu-latest)
🔇 Additional comments (1)
.github/workflows/docker-edge.yml (1)
14-15
: Verify path filter coverage for server-related files.The path filter ensures that the workflow runs only when changes are made to
packages/sync-server
. This aligns with the PR objective of optimizing server workflows.Run the following script to verify if there are any server-related files outside the
packages/sync-server
directory:✅ Verification successful
🏁 Script executed:
#!/bin/bash # Description: Search for server-related files outside packages/sync-server. # Test: Search for server-related files. Expect: No server files outside packages/sync-server. fd -t f -E 'packages/sync-server' -E '.git' -E 'node_modules' \ --exec rg -l -i 'server|express|http|api|endpoint|route|middleware'Length of output: 57260
Path Filter Verification for sync-server Workflow
The script confirms that many files contain server-related keywords outside of the
packages/sync-server
directory. This is expected because the workflow in.github/workflows/docker-edge.yml
is intentionally scoped to trigger only on changes insidepackages/sync-server
—aligning with the PR’s objective of optimizing server workflows by focusing exclusively on that component.
- The current filter excludes other server-related files (e.g., those in
packages/api
orpackages/loot-core/src/server
), which is the intended behavior.
Running the server workflows only when server files are changed.
The docker images take a while to build, this should speed up most PR's.