Repository navigation
Run CI once, and only when the app changes - #4
Merged
Merged
Conversation
CI now runs on pull requests only, not again after merging. The windows and linux jobs are skipped unless src-tauri/, ui/ or the npm package files changed; skipped jobs still satisfy main's required checks. The CI badge follows pull request runs, since main no longer has its own.
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.
CI now runs once per pull request instead of again after merging, and the Windows and Linux builds only run when
src-tauri/,ui/or the npm package files change.Skipped jobs still report a result, so
main's required checks don't wait for them. If the list of changed files can't be read, the builds run anyway.This pull request doesn't touch the app, so it should skip both builds.