Skip to content

chore: add PR/issue templates, SECURITY.md, CodeQL, dependabot configurator - #592

Merged
jackgranatowski merged 2 commits into
mainfrom
claude/pr-templates-github-config-r2o761
Jul 11, 2026
Merged

chore: add PR/issue templates, SECURITY.md, CodeQL, dependabot configurator#592
jackgranatowski merged 2 commits into
mainfrom
claude/pr-templates-github-config-r2o761

Conversation

@jackgranatowski

Copy link
Copy Markdown
Contributor

Bring the framework repo's GitHub configuration up to parity with
SLASHED-Plugins:

  • Add PULL_REQUEST_TEMPLATE.md with a checklist mirroring the CI gates
    (lint:css, build, test, check:version, check:llm-guide, check:macros,
    check:registry, audit:check, CHANGELOG, migration docs).
  • Add ISSUE_TEMPLATE/ (bug_report, feature_request, config) with a
    cross-link to SLASHED-Plugins and blank issues disabled.
  • Add SECURITY.md advertising the private advisory channel that
    SLASHED-Plugins already points framework vulnerabilities to.
  • Add CodeQL workflow (javascript-typescript + actions).
  • Extend dependabot to cover the /configurator npm package.

Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01UPjqiNnKXeQPhcdu93krL5

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jackgranatowski, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: aaa34ffc-8772-43c2-a82f-05410d070fbb

📥 Commits

Reviewing files that changed from the base of the PR and between 23962f5 and 521df14.

📒 Files selected for processing (6)
  • .github/ISSUE_TEMPLATE/bug_report.yml
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/feature_request.yml
  • .github/PULL_REQUEST_TEMPLATE.md
  • .github/dependabot.yml
  • SECURITY.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/pr-templates-github-config-r2o761

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Jul 11, 2026

Copy link
Copy Markdown

Greptile Summary

This PR brings the framework repo's GitHub configuration up to parity with SLASHED-Plugins by adding community health files and security tooling — all additive, no runtime code changes.

  • Issue templates & PR template: Structured YAML issue forms (bug, feature request) with blank_issues_enabled: false, a config.yml routing plugin/security reports to the right repos, and a PR checklist that accurately mirrors every CI gate documented in CLAUDE.md (lint:css, build, test, check:version, check:llm-guide, check:macros, check:registry, audit:check).
  • CodeQL workflow: Scans javascript-typescript and actions on push/PR/scheduled Monday run; action steps are SHA-pinned for supply-chain safety and security-extended queries are enabled.
  • Dependabot + SECURITY.md: Adds /configurator npm ecosystem to weekly Dependabot scans (consistent with CLAUDE.md's version-sync requirements) and documents the private advisory channel for vulnerability reports.

Confidence Score: 5/5

All changes are additive GitHub configuration files with no runtime code — safe to merge.

Every file added is a community health or CI configuration file: issue templates, a PR checklist, a CodeQL workflow with SHA-pinned actions, an extended Dependabot config, and a SECURITY.md. None touch source code or build artifacts. The PR checklist faithfully reflects the CI gates described in CLAUDE.md, and the CodeQL workflow follows recommended structure for interpreted languages.

No files require special attention — all changes are documentation and workflow configuration.

Important Files Changed

Filename Overview
.github/workflows/codeql.yml New CodeQL workflow scanning javascript-typescript and actions on push/PR/schedule with SHA-pinned action references; no build step needed for JS/TS, correct structure.
.github/dependabot.yml Adds /configurator npm ecosystem entry to weekly Dependabot scans, matching CLAUDE.md requirement to keep the configurator package in sync.
.github/PULL_REQUEST_TEMPLATE.md New PR template with checklist accurately mirroring CI gates (lint:css, build, test, check:version, check:llm-guide, check:macros, check:registry, audit:check).
.github/ISSUE_TEMPLATE/bug_report.yml New structured bug report template with required fields for reproduction steps, version, and environment.
.github/ISSUE_TEMPLATE/feature_request.yml New feature request template with categorized area dropdown and optional alternatives field.
.github/ISSUE_TEMPLATE/config.yml Disables blank issues and redirects plugin/security reports to the correct repos.
SECURITY.md New security policy directing reporters to GitHub private advisories and clearly scoping plugin vs. framework vulnerabilities.

Reviews (1): Last reviewed commit: "chore: add PR/issue templates, SECURITY...." | Re-trigger Greptile

claude added 2 commits July 11, 2026 06:54
…urator

Bring the framework repo's GitHub configuration up to parity with
SLASHED-Plugins:

- Add PULL_REQUEST_TEMPLATE.md with a checklist mirroring the CI gates
  (lint:css, build, test, check:version, check:llm-guide, check:macros,
  check:registry, audit:check, CHANGELOG, migration docs).
- Add ISSUE_TEMPLATE/ (bug_report, feature_request, config) with a
  cross-link to SLASHED-Plugins and blank issues disabled.
- Add SECURITY.md advertising the private advisory channel that
  SLASHED-Plugins already points framework vulnerabilities to.
- Add CodeQL workflow (javascript-typescript + actions).
- Extend dependabot to cover the /configurator npm package.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UPjqiNnKXeQPhcdu93krL5
The advanced-setup codeql.yml conflicted with the CodeQL default setup
already enabled on this repo, producing a "configuration error" and
failing the Analyze jobs on the PR. Default setup already scans the repo
(its Analyze jobs pass), so an explicit workflow is redundant here —
unlike SLASHED-Plugins, which needs an advanced workflow for paths-ignore
over committed build artifacts. Remove the workflow to clear the conflict.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UPjqiNnKXeQPhcdu93krL5
@jackgranatowski
jackgranatowski force-pushed the claude/pr-templates-github-config-r2o761 branch from 0c16feb to 521df14 Compare July 11, 2026 06:55
@jackgranatowski
jackgranatowski merged commit ebacd9a into main Jul 11, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants