Re: [PATCH] ci: respect the [skip ci] convention in our GitHub workflow "CI/PR"

From: Jeff King <peff@peff.net>
Date: May 4, 2020, 15:01 UTC
Message-ID: <20200504150105.GB11373@coredump.intra.peff.net>
In-Reply-To: <20200503120546.GB28680@danh.dev>

On Sun, May 03, 2020 at 07:05:46PM +0700, Danh Doan wrote:

Show 24 quoted lines

> This is my proposal for it:
> [...]
> diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> index fd4df939b5..303393ba73 100644
> --- a/.github/workflows/main.yml
> +++ b/.github/workflows/main.yml
> @@ -1,6 +1,19 @@
>  name: CI/PR
>  
> -on: [push, pull_request]
> +on:
> +  pull_request:
> +    branches:
> +      - '*'
> +  push:
> +    branches:
> +      - maint
> +      - master
> +      - next
> +      - jch
> +      - pu
> +      - 'for-ci/**'
> +    tags:
> +      - '*'

Yeah, this seems quite reasonable to me. I'd just add a refspec to push a duplicate of branches I'm interested in running CI on to for-ci.

-Peff

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.