Skip to content

ci: run the workflows for eve/ branches - #11

Merged
rucoder merged 1 commit into
eve/v0.26.0from
rucoder/ci-eve-branches
Oct 23, 2026
Merged

rucoder merged 1 commit into
eve/v0.26.0from
rucoder/ci-eve-branches

Conversation

@rucoder

@rucoder rucoder commented Oct 23, 2026

Copy link
Copy Markdown

The fmtcheck, lint and test workflows trigger only on main (branches: [ main ] for both push and pull_request), so PRs against eve/v0.26.0 such 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.

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>
@rucoder
rucoder merged commit 95cd0c1 into eve/v0.26.0 Oct 23, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants