Skip to content

docs: populate PR template#264

Open
wozos wants to merge 1 commit into
logos-co:mainfrom
wozos:wozos/claude/pr-template-20260515-183601
Open

docs: populate PR template#264
wozos wants to merge 1 commit into
logos-co:mainfrom
wozos:wozos/claude/pr-template-20260515-183601

Conversation

@wozos
Copy link
Copy Markdown
Contributor

@wozos wozos commented May 15, 2026

Summary

Populates the previously empty .github/pull_request_template.md with the minimal set of fields needed for a docs-first repo:

  • Linked issue
  • Summary of changes
  • Target doc type (the five canonical types from CONTRIBUTING.md)
  • Target quality level (mirrors the quality:* label taxonomy)
  • Checklist for lint and link checks (uses the Makefile targets called out in .github/copilot-instructions.md)

17 lines, terse style to match other files under .github/.

Test plan

  • On opening a new PR, the template renders as the default description.
  • Headings and checklist boxes appear correctly.
  • Lint/link commands in the checklist match what .github/copilot-instructions.md describes.

🤖 Generated with Claude Code

Add sections for linked issue, summary, doc type, quality level, and a
lint/links checklist. Document type and quality level options mirror
the taxonomy in CONTRIBUTING.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@@ -0,0 +1,17 @@
## Linked issue
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this template is more for us to discuss on what would work best for the team

@logos-co/docs @logos-co/eco-dev-eng

@cheny0
Copy link
Copy Markdown
Contributor

cheny0 commented May 18, 2026

Let's remove the empty template for now because the doc packet template is serving the purpose. Thanks!

@weboko
Copy link
Copy Markdown
Contributor

weboko commented May 19, 2026

@cheny0 this template file is what gets automatically prefilled when someone opens a PR

we can add a checklist to, for example, not forget to use https://github.com/logos-co/logos-docs/blob/main/resources/templates/doc-packet.md or some other criteria that must happen for someone to review the PR

do you still think better not to have a template?

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.

3 participants