Skip to content

fix(forms): correct issue template project schema (closes #56)#60

Merged
thenarfer merged 1 commit intomainfrom
09-18-fix_forms_correct_issue_template_project_schema
Sep 19, 2025
Merged

fix(forms): correct issue template project schema (closes #56)#60
thenarfer merged 1 commit intomainfrom
09-18-fix_forms_correct_issue_template_project_schema

Conversation

@thenarfer
Copy link
Copy Markdown
Owner

@thenarfer thenarfer commented Sep 18, 2025


name: "Tech Debt / Chore PR"

about: "Refactor, cleanups, dep bumps, infra chores"

Why now

Risk reduction and maintainability by simplifying project references in issue templates.

Scope

Updated project references in all issue templates (bug, feature, sprint-plan, tech-debt).

Change

  • Simplified project references from verbose URL format with workflow to shorthand thenarfer/1 format
  • Standardized project reference location in all templates
  • Removed redundant workflow references

Validation

  • No user-visible behavior change
  • User-visible impact: none
  • CI green; tests updated if needed
  • Perf impact considered (none)
  • Security/secrets considered (none)
  • Docs updated if user-visible

Evidence (before/after, logs, links)

Before:

projects:
  - url: https://github.com/users/thenarfer/projects/1
    workflow: .github/workflows/add-to-project.yml

After:

projects:
  - thenarfer/1


See docs/DoR.md & docs/DoD.md.

Closes #56

Summary by CodeRabbit

  • Chores
    • Simplified project linking in all issue templates (Bug, Feature, Sprint Plan, Tech Debt) to use a direct repository project reference.
    • New issues created from templates will attach to the intended project consistently without per-template workflow config.
    • Minor template cleanup; no changes to the fields users complete when filing issues.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Sep 18, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Updated four GitHub Issue Templates to convert their projects entries from objects with url/workflow into simple repository-string references (thenarfer/1); no other template fields were changed.

Changes

Cohort / File(s) Summary
Issue templates: projects schema update
.github/ISSUE_TEMPLATE/bug.yml, .github/ISSUE_TEMPLATE/feature.yml, .../sprint-plan.yml, .../tech-debt.yml
Replace projects entries that used mappings (url, workflow) with a flat string list item thenarfer/1; in some files the projects block was moved to top-level. No other content modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

priority:P2, type:chore, size:XS, area:process

Poem

I hop through YAML fields so bright,
Swapping maps for strings at night—
A tidy thenarfer/1 in place,
No more broken project chase.
Thump-thump! Templates light and tight. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Title Check ✅ Passed The title succinctly and accurately summarizes the primary change—correcting the issue template project schema—and matches the PR description and file diffs. It is concise, uses a conventional commit scope ("forms"), and clearly communicates intent to reviewers. Including "closes #56" appropriately links the PR to the tracked issue.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b918567 and 24639d8.

📒 Files selected for processing (4)
  • .github/ISSUE_TEMPLATE/bug.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/feature.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/sprint-plan.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/tech-debt.yml (2 hunks)

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

Copy link
Copy Markdown
Owner Author

thenarfer commented Sep 18, 2025

@thenarfer
Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Sep 18, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
.github/ISSUE_TEMPLATE/feature.yml (1)

106-106: Add a trailing newline (YAMLlint error).

File is missing a newline at EOF; fix to satisfy lint/checkers.

Apply this diff:

 projects:
   - thenarfer/1
+
.github/ISSUE_TEMPLATE/sprint-plan.yml (1)

117-117: Add a trailing newline (YAMLlint error).

Missing newline at EOF; add one to clear lint.

 projects:
   - thenarfer/1
+
.github/ISSUE_TEMPLATE/tech-debt.yml (2)

25-25: Trim stray whitespace.

Remove the trailing spaces on this otherwise blank line to keep diffs clean.

-      
+

77-78: Shorthand project reference approved; add trailing newline.

Schema change LGTM; also add a newline at EOF to satisfy lint.

 projects:
   - thenarfer/1
+
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0d973ec and b918567.

📒 Files selected for processing (4)
  • .github/ISSUE_TEMPLATE/bug.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/feature.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/sprint-plan.yml (1 hunks)
  • .github/ISSUE_TEMPLATE/tech-debt.yml (2 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/ISSUE_TEMPLATE/feature.yml

[error] 106-106: no new line character at the end of file

(new-line-at-end-of-file)

.github/ISSUE_TEMPLATE/sprint-plan.yml

[error] 117-117: no new line character at the end of file

(new-line-at-end-of-file)

.github/ISSUE_TEMPLATE/tech-debt.yml

[error] 78-78: no new line character at the end of file

(new-line-at-end-of-file)

🔇 Additional comments (3)
.github/ISSUE_TEMPLATE/feature.yml (1)

105-106: Shorthand project reference looks good.

Switching to thenarfer/1 simplifies maintenance and removes workflow coupling.

.github/ISSUE_TEMPLATE/bug.yml (1)

42-42: Project mapping → shorthand is correct.

projects: - thenarfer/1 is the expected schema; no further changes needed here.

.github/ISSUE_TEMPLATE/sprint-plan.yml (1)

116-117: Standardized project reference — good move.

Consistent with other templates and easier to maintain.

@thenarfer thenarfer changed the title fix(forms): correct issue template project schema fix(forms): correct issue template project schema (closes #56) Sep 19, 2025
Copy link
Copy Markdown
Owner Author

thenarfer commented Sep 19, 2025

Merge activity

  • Sep 19, 8:50 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Sep 19, 8:52 AM UTC: Graphite couldn't merge this PR because it had merge conflicts.

@thenarfer thenarfer changed the base branch from fix/issue-template-project-schema to graphite-base/60 September 19, 2025 08:51
@thenarfer thenarfer changed the base branch from graphite-base/60 to main September 19, 2025 08:51
Corrects the schema for the  key in issue templates
to prevent validation errors and ensure future compatibility.

Closes #56
@thenarfer thenarfer force-pushed the 09-18-fix_forms_correct_issue_template_project_schema branch from b918567 to 24639d8 Compare September 19, 2025 12:38
@thenarfer thenarfer merged commit a2edb26 into main Sep 19, 2025
6 of 7 checks passed
@thenarfer thenarfer deleted the 09-18-fix_forms_correct_issue_template_project_schema branch September 19, 2025 12:39
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.

chore(forms): fix project schema in issue templates

1 participant