You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@commons.apache.org by GitBox <gi...@apache.org> on 2026/09/17 20:30:06 UTC
[GH] (commons-jelly/master): Workflow run "maven in /jelly-tags/quartz for log4j:log4j - Update #1580734187" failed!
The GitHub Actions job "maven in /jelly-tags/quartz for log4j:log4j - Update #1580734187" on commons-jelly.git/master has failed.
Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]).
Head commit for run:
1cee2971a201411c39e6d1606d7d7d22fad52501 / Aurélien Pupier <ap...@ibm.com>
Restrict trigger push branch for GitHub Workflow (#106)
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.
see https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408443#GitHubActionsRecommendedPractices-Restrictthepushtriggertospecificbranches
Signed-off-by: Aurélien Pupier <ap...@ibm.com>
Report URL: https://github.com/apache/commons-jelly/actions/runs/35271085855
With regards,
GitHub Actions via GitBox