如何当Issue已有标签时跳过GitHub Actions任务

你可以通过以下几种方式实现「Issue已有标签时不执行CI或跳过任务/步骤」的需求：

1. 直接不触发整个Workflow（最节省资源） #

在Workflow的触发条件中添加判断，仅当Issue没有任何标签时才触发：

name: "Labeler"
on:
  issues:
    types: [ opened, edited, reopened ]
    # 判断Issue的标签数组长度为0，即无标签
    if: ${{ github.event.issue.labels | length == 0 }}

jobs:
  triage:
    runs-on: ubuntu-latest
    name: Label issues
    steps:
      - name: check out
        uses: actions/checkout@v3

      - name: labeler
        uses: jbinda/super-labeler-action@develop
        with:
          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"

2. 触发Workflow但跳过整个triage任务 #

如果需要触发Workflow但跳过标签处理任务，可在job级别添加条件判断：

name: "Labeler"
on:
  issues:
    types: [ opened, edited, reopened ]

jobs:
  triage:
    runs-on: ubuntu-latest
    name: Label issues
    # 仅当Issue无标签时执行该任务
    if: ${{ github.event.issue.labels | length == 0 }}
    steps:
      - name: check out
        uses: actions/checkout@v3

      - name: labeler
        uses: jbinda/super-labeler-action@develop
        with:
          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"

3. 仅跳过labeler步骤（保留其他步骤执行） #

如果需要执行checkout等前置步骤，但仅跳过标签处理操作，可在步骤级别添加条件：

name: "Labeler"
on:
  issues:
    types: [ opened, edited, reopened ]

jobs:
  triage:
    runs-on: ubuntu-latest
    name: Label issues
    steps:
      - name: check out
        uses: actions/checkout@v3

      - name: labeler
        # 仅当Issue无标签时执行该步骤
        if: ${{ github.event.issue.labels | length == 0 }}
        uses: jbinda/super-labeler-action@develop
        with:
          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"

说明 #

• github.event.issue.labels 是GitHub事件中携带的Issue标签数组，通过length过滤器判断是否有标签。
• 三种方案可根据实际需求选择：若完全不需要处理带标签的Issue，优先选方案一；若需保留Workflow触发但跳过核心任务，选方案二；若需保留前置步骤，选方案三。

内容的提问来源于stack exchange，提问作者L2ncE