From ef845cf9667f783e44dec13ffb2d10d02bbac923 Mon Sep 17 00:00:00 2001 From: "Andres G. Aragoneses" Date: Fri, 7 Oct 2022 10:29:14 +0800 Subject: [PATCH] GitHubActions: don't restrict CI to master branch There's no point about restricting CI to master branch; doing this will prevent contributors to know the CI status (e.g. the result from running unit tests after their proposed contributions) before they propose a PullRequest; because normally people create branches when they want to start to work on something (instead of having to use the master branch of their fork). --- .github/workflows/master.yml | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/.github/workflows/master.yml b/.github/workflows/master.yml index baf6e8461f..d5ab189b01 100644 --- a/.github/workflows/master.yml +++ b/.github/workflows/master.yml @@ -1,15 +1,7 @@ name: CI -# Controls when the action will run. -on: - # Triggers the workflow on push or pull request events but only for the master branch - push: - branches: [ master ] - pull_request: - branches: - - master - # Allows you to run this workflow manually from the Actions tab - workflow_dispatch: +on: [push, pull_request, workflow_dispatch] + env: DOTNET_CLI_TELEMETRY_OPTOUT: 'true' # A workflow run is made up of one or more jobs that can run sequentially or in parallel