You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2026/06/30 20:07:00 UTC

[jira] [Assigned] (NIFI-16057) Restrict trigger push branch for GitHub Workflow

     [ https://issues.apache.org/jira/browse/NIFI-16057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann reassigned NIFI-16057:
---------------------------------------

    Assignee: Aurélien Pupier

> Restrict trigger push branch for GitHub Workflow
> ------------------------------------------------
>
>                 Key: NIFI-16057
>                 URL: https://issues.apache.org/jira/browse/NIFI-16057
>             Project: Apache NiFi
>          Issue Type: Task
>            Reporter: Aurélien Pupier
>            Assignee: Aurélien Pupier
>            Priority: Major
>             Fix For: 2.11.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> 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)