andygrove opened a new pull request, #90:
URL: https://github.com/apache/datafusion-java/pull/90
## Which issue does this PR close?
- No tracking issue.
## Rationale for this change
\`.github/workflows/build.yml\` currently listens on \`main\` only:
\`\`\`yaml
on:
push:
branches: [main]
pull_request:
branches: [main]
\`\`\`
So pushes to \`branch-0.1\` (and any future \`branch-*\` release branch)
don't trigger CI, and PRs targeting those branches — e.g. release-prep PRs that
bump the version or land changelog updates — get merged without the test suite
ever running. The first such PR (#89, against \`branch-0.1\`) made this visible.
## What changes are included in this PR?
Add \`'branch-*'\` (quoted because of the glob) to both trigger lists:
\`\`\`yaml
on:
push:
branches: [main, 'branch-*']
pull_request:
branches: [main, 'branch-*']
\`\`\`
No other changes to the workflow — the same single \`make test\` job runs.
## Are these changes tested?
The change itself is exercised by GitHub Actions accepting the workflow file
when this PR is opened (the workflow is re-parsed on every push). The pattern
\`branch-*\` matches \`branch-0.1\`, \`branch-0.2\`, etc.; verified by GitHub's
filter docs and by the analogous pattern used in several other Apache projects'
workflows.
## Are there any user-facing changes?
No.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
