mirror of
https://github.com/DarkFlippers/unleashed-firmware.git
synced 2026-11-13 12:37:33 +00:00
Mykhailo Shevchuk
7898b15d8a
PR template: port the "No AI assistance" option and the "tick exactly one" note
from all-the-plugins (xMasterX/all-the-plugins#249) so the two repos agree, and
add a check that fails the PR unless exactly one of the three boxes is ticked.
The check needs no token and checks out nothing (`permissions: {}`), so plain
`pull_request` is safe for forks; `edited` is in the trigger list so fixing the
description re-runs it.
pr-build.yml: #1052 bound github.head_ref/ref_name to env, but the branch name
still reached a `run:` block through steps.vars.outputs.ref/.dist, which the
"Assemble PR report" step interpolated. A branch named `x$(id)` still executed
there. Bind those outputs to env as well, and reduce SAFE_REF to
[A-Za-z0-9._-] instead of only replacing '/', so the outputs are inert for
every consumer. Artifact names are unchanged for ordinary branch names.
Pin the two third-party actions to commits: dessant/lock-threads runs with
issues+pull-requests write, and a mutable tag can be repointed at any time.
51 lines
2.0 KiB
YAML
51 lines
2.0 KiB
YAML
# Lock closed issues and PRs after a period of inactivity, so stale threads
|
|
# don't accumulate "me too" / necro comments that never reach a maintainer.
|
|
# Locking is not closing: it only stops new comments, and anyone can still open
|
|
# a fresh issue from the templates. The bot never auto-closes anything.
|
|
#
|
|
# Runs once a day (dessant recommends daily to keep resource use low) and can be
|
|
# kicked off by hand via workflow_dispatch. Each thread type only gets processed
|
|
# when its *-inactive-days is set, so issues and PRs are opted in explicitly below.
|
|
|
|
name: Lock threads
|
|
|
|
on:
|
|
schedule:
|
|
- cron: "0 3 * * *" # daily, 03:00 UTC (off-peak)
|
|
workflow_dispatch:
|
|
|
|
# Locking edits issue/PR state; no code is checked out or executed. Everything
|
|
# unlisted is denied.
|
|
permissions:
|
|
issues: write
|
|
pull-requests: write
|
|
|
|
# One sweep at a time; a manual run and the nightly cron shouldn't overlap.
|
|
concurrency:
|
|
group: lock-threads
|
|
cancel-in-progress: false
|
|
|
|
jobs:
|
|
lock:
|
|
name: Lock inactive closed threads
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
# Third-party action pinned to a commit: this job holds issues+PRs write, and a
|
|
# mutable tag can be repointed at any time. Bump deliberately, not implicitly.
|
|
- uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6
|
|
with:
|
|
issue-inactive-days: "14"
|
|
pr-inactive-days: "14"
|
|
issue-comment: >
|
|
This issue has been automatically locked since there has been no
|
|
activity for a while after it was closed. If you're hitting the same
|
|
problem, please open a new issue with up-to-date details and your
|
|
firmware version.
|
|
pr-comment: >
|
|
This pull request has been automatically locked since there has been
|
|
no activity for a while after it was closed. If you'd like to pick
|
|
this up, please open a new issue or PR.
|
|
# Default reason "resolved" fits closed-then-idle threads.
|
|
issue-lock-reason: resolved
|
|
pr-lock-reason: resolved
|