Restrict trigger push branch for GitHub Workflow
Feature branches rarely need their own CI runs: the code is already tested when a pull request is opened against a release branch. If the push trigger has no branch restriction and pull_request is also configured, every push to a branch with an open PR runs the workflow twice: once for the push and once for the PR synchronisation.
Always give the push trigger an explicit list of branches: this stops branches created from a release branch from inheriting its workflow runs.
Signed-off-by: Aurélien Pupier apupier@ibm.com
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Apache BVal - Apache’s implementation of the Jakarta Validation specification for Jakarta EE and Java SE
Branches
master / 3.1.x
Jakarta Validation 3.1 implementation (Jakarta EE 11), requires Java 17+.
3.0.x
Jakarta Bean Validation 3.0 implementation (Jakarta EE 10), requires Java 11+.
2.x
Bean Validation 2.0 (JSR-380) implementation (Java EE 8), requires Java 8+.
1.1.x
Bean Validation 1.1 (JSR-349) implementation (Java EE 7), requires Java 6+.
Minimum Requirements (master)
Installation
Usage
Dependency
Optional: extra constraints
Optional: OSGi bundle
Basic usage
More Information
Please visit https://bval.apache.org for full documentation and release notes.
Issue tracker: https://issues.apache.org/jira/browse/BVAL