You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Aurélien Pupier (Jira)" <ji...@apache.org> on 2026/06/30 12:24:00 UTC
[jira] [Created] (RANGER-5659) Configure GitHub workflows to restrict the push trigger to specific branches
Aurélien Pupier created RANGER-5659:
---------------------------------------
Summary: Configure GitHub workflows to restrict the push trigger to specific branches
Key: RANGER-5659
URL: https://issues.apache.org/jira/browse/RANGER-5659
Project: Ranger
Issue Type: Task
Components: build-infra
Reporter: Aurélien Pupier
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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)