Repository navigation
ci: run the workflows for eve/ branches - #11
Merged
Merged
Conversation
The fmtcheck, lint and test workflows ran only for pushes and pull requests to main, so nothing checked the eve/<upstream tag> branches EVE builds from, or the pull requests against them. Run them for eve/** as well. This is the fork's own change, not one for upstream: like the module rename, it goes on top of EVE's patches whenever a new eve/<tag> branch is cut. Signed-off-by: Mikhail Malyshev <mike.malyshev@gmail.com>
christoph-zededa
approved these changes
Oct 23, 2026
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.
The fmtcheck, lint and test workflows trigger only on
main(branches: [ main ]for bothpushandpull_request), so PRs againsteve/v0.26.0such as #9 and #10 got no checks at all. This adds'eve/**'to the six branch filters.For pull requests GitHub reads the workflows from the PR's merge commit, so this PR runs its own checks. Once it is merged, every PR against an
eve/branch, #9 included, is checked on its next push, and so is every push to these branches.It is a fork-only change: like the module rename, it is not for upstream, and it goes on top of EVE's patches whenever a new
eve/<tag>branch is cut.