Skip to content

chore: drop URL output requirement from PR status summary#328

Closed
JacobPEvans wants to merge 1 commit into
mainfrom
chore/drop-url-output-requirement
Closed

chore: drop URL output requirement from PR status summary#328
JacobPEvans wants to merge 1 commit into
mainfrom
chore/drop-url-output-requirement

Conversation

@JacobPEvans
Copy link
Copy Markdown
Owner

Summary

  • #42 style refs are already clickable in Ghostty / Claude Code, so the full https://github.com/<OWNER>/<REPO>/pull/N URL in every PR status summary was redundant noise.
  • Remove URL output from all three sections of the Canonical PR Status Summary in gh-cli-patterns; PRs are now identified by #N.
  • Drop the "Fetch PR URL" subsection and the matching gh pr view ... --json url block in /ship.
  • Strip the now-unused url field from the open-PR GraphQL query.

Pure removal — no new instructions, no format additions beyond the #N ref the user explicitly named as the replacement.

Test plan

  • /ship and /finalize-pr summaries render with #N refs and remain clickable in Ghostty
  • No remaining https://github.com/<OWNER>/<REPO>/pull/ placeholders in github-workflows/skills/

GitHub PR/issue refs like #42 are already clickable in Ghostty and
Claude Code, so the full https://github.com/... URL was redundant
output. Strip the URL from the Canonical PR Status Summary format,
the matching fetch instruction in /ship, and the now-unused `url`
field from the GraphQL query.

Assisted-by: Claude <noreply@anthropic.com>
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the Canonical PR Status Summary pattern to use PR numbers instead of full URLs across documentation and examples. This includes removing unnecessary URL-fetching commands and GraphQL fields from the gh-cli-patterns and ship skill documentation. A review comment suggests clarifying the separator convention for status tags to resolve inconsistencies between the instructions and the provided examples.

Comment thread github-workflows/skills/gh-cli-patterns/SKILL.md
@JacobPEvans
Copy link
Copy Markdown
Owner Author

Changed my mind, this is not a good change.

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