(tinkerpop) branch master updated: Restrict trigger push branch for GitHub Workflow (#3500)

[co...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

Cole-Greer pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git


The following commit(s) were added to refs/heads/master by this push:
     new eab8d7fecb Restrict trigger push branch for GitHub Workflow (#3500)
eab8d7fecb is described below

commit eab8d7fecb3b5d6dc78abafaacf9487384fcccd9
Author: Aurélien Pupier <ap...@ibm.com>
AuthorDate: Wed Jul 8 00:22:56 2026 +0200

    Restrict trigger push branch for GitHub Workflow (#3500)
    
    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
    
    ignoring only dependabot branches as it seems that several feature
    branches are created on the main Apache tinkerpop repository. The
    dependabot case should already cut most if the duplicate workload
    
    Signed-off-by: Aurélien Pupier <ap...@ibm.com>
---
 .github/workflows/build-test.yml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/build-test.yml b/.github/workflows/build-test.yml
index 2efb1dff5e..0f8f7aecad 100644
--- a/.github/workflows/build-test.yml
+++ b/.github/workflows/build-test.yml
@@ -1,5 +1,9 @@
 name: build-test
-on: [push, pull_request]
+on:
+  push:
+    branches-ignore:
+      - dependabot/**
+  pull_request:
 env:
   # modules commonly excluded from builds as they have their own independent non-JVM setups and can be run in parallel.
   # take care when modifying this list because GLVs use shell commands to remove themselves from this list and