Skip to content

chore: sync issue/PR templates from repo-scaffold - #26

Open
blairg23 wants to merge 8 commits into
mainfrom
chore/sync-templates
Open

blairg23 wants to merge 8 commits into
mainfrom
chore/sync-templates

Conversation

@blairg23

Copy link
Copy Markdown
Owner

🧾 Title

Sync issue/PR templates from repo-scaffold

🧠 Description

This PR was opened automatically by repo-scaffold sync templates because one or more of this repo's issue/PR templates have drifted from the current canonical versions repo-scaffold generates.

🧩 Changes Included

  • Added/updated documentation

🎯 Purpose

Keep downstream templates current with repo-scaffold's own canonical versions, the same way Dependabot keeps dependencies current -- never committed directly to the default branch.

🔗 Files Changed

  • .github/CODEOWNERS
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/epic.md
  • .github/ISSUE_TEMPLATE/ticket.md
  • .github/pull_request_template.md
  • .github/workflows/validate-issue.yml
  • .github/workflows/validate-pr-sop.yml
  • .github/workflows/validate-pr.yml

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7ab6e85228

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/workflows/validate-issue.yml Resolved
blairg23 added a commit to blairg23/repo-scaffold that referenced this pull request Sep 2, 2026
…notice on every edit

validate-issue.yml fires on issues: [opened, edited]. When an issue stays
malformed across multiple edits, every edited event reached an
unconditional createComment call, so the issue accumulated one duplicate
notice per edit. validate-pr.yml had the exact same bug (#301) and
already has the fix (check existing comments for the marker before
posting); validate-issue.yml never got the equivalent change even though
it's the same pattern in the sibling file.

Mirrors #301's fix exactly: paginate existing comments, check whether a
bot comment already contains the MISSING_SECTIONS_MARKER text, and skip
posting if so. Applied to both the canonical template
(src/repo_scaffold/templates/github/workflows/validate-issue.yml) and
this repo's own live copy (.github/workflows/validate-issue.yml), which
were still in sync with each other pre-fix -- same class of drift #259
fixed for validate-pr.yml.

Surfaced by automated review on five separate sync templates PRs across
downstream repos (blairg23/cuequeue#26, blairg23/gallery-dl-wrapper#26,
blairg23/marquee#46, blairg23/signet#46, blairg23/spotdl-wrapper#18) --
a bug in the canonical template, not specific to any one repo. Those PRs
will pick up the fix once this merges and sync templates re-runs.

Closes #309.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
blairg23 added a commit to blairg23/repo-scaffold that referenced this pull request Oct 23, 2026
…notice on every edit

validate-issue.yml fires on issues: [opened, edited]. When an issue stays
malformed across multiple edits, every edited event reached an
unconditional createComment call, so the issue accumulated one duplicate
notice per edit. validate-pr.yml had the exact same bug (#301) and
already has the fix (check existing comments for the marker before
posting); validate-issue.yml never got the equivalent change even though
it's the same pattern in the sibling file.

Mirrors #301's fix exactly: paginate existing comments, check whether a
bot comment already contains the MISSING_SECTIONS_MARKER text, and skip
posting if so. Applied to both the canonical template
(src/repo_scaffold/templates/github/workflows/validate-issue.yml) and
this repo's own live copy (.github/workflows/validate-issue.yml), which
were still in sync with each other pre-fix -- same class of drift #259
fixed for validate-pr.yml.

Surfaced by automated review on five separate sync templates PRs across
downstream repos (blairg23/cuequeue#26, blairg23/gallery-dl-wrapper#26,
blairg23/marquee#46, blairg23/signet#46, blairg23/spotdl-wrapper#18) --
a bug in the canonical template, not specific to any one repo. Those PRs
will pick up the fix once this merges and sync templates re-runs.

Closes #309.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.

1 participant