Files
unleashed-firmware/.github/pull_request_template.md
T
Mykhailo Shevchuk 7898b15d8a CI: require the AI usage disclosure and finish the shell-injection hardening (#1054)
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.
2026-07-28 21:56:21 +03:00

1.0 KiB

What's new

  • [ Describe changes here ]

Verification

  • [ Describe how to verify changes ]

Author Checklist (Fill this out):

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if it exists)

AI usage disclosure (Fill this out):

Tick exactly one - leaving all three blank reads as "not filled out" rather than "no AI".

  • No AI assistance.

  • Partially AI assisted (clarify below which code was AI assisted and briefly explain what it does).

  • Fully AI generated (explain what all the generated code does in moderate detail).

  • [ Describe how AI was used in this PR if it was used ]

Checklist (For Reviewer) (Don't fill this out!):

  • PR has proper description of new feature/bugfix
  • Description contains actions to verify feature/bugfix on the hardware
  • No obvious issues with the code was found
  • I've built this code, uploaded it to the device and verified feature/bugfix