# While a new geometry kernel is evaluated, new issues and discussions about kernel work, and new
# pull requests that change the kernel directories, are labelled `kernel-paused` for a maintainer to
# answer (CONTRIBUTING.md, "Kernel work is paused"). The logic is in scripts/kernel-paused/ (tested
# in ci.yml).
name: Kernel paused

on:
  issues:
    types: [opened]
  # pull_request_target so PRs from forks can be labelled. It runs the base branch's
  # scripts/kernel-paused and only lists the PR's changed paths; the PR's code is never checked out.
  pull_request_target:
    types: [opened]
  discussion:
    types: [created]

permissions:
  contents: read # to check out scripts/kernel-paused
  issues: write
  pull-requests: write # to list a PR's changed paths and add its label
  discussions: write

concurrency:
  group: kernel-paused-${{ github.event.issue.number || github.event.pull_request.number || github.event.discussion.number }}
  cancel-in-progress: false

jobs:
  paused:
    name: Kernel paused bot
    runs-on: ubuntu-24.04
    timeout-minutes: 10
    steps:
      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
        with:
          sparse-checkout: scripts/kernel-paused
      - uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
        with:
          script: |
            const paused = require('./scripts/kernel-paused/kernel-paused.js');
            const done = context.eventName === 'discussion'
              ? await paused.handleDiscussion({ github, context })
              : await paused.handleOpened({ github, context });
            core.info(done);