Skip to content

Conversation

@aimeeu
Copy link
Contributor

@aimeeu aimeeu commented Dec 3, 2025

  • Include Runtime label query parm in link to Nomad PR template
  • Update Nomad PR template with additional instructions

@aimeeu aimeeu requested a review from a team as a code owner December 3, 2025 18:26
@aimeeu aimeeu requested a review from rmainwork December 3, 2025 18:26
@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Thu Dec 4 17:18:41 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Thu Dec 4 17:13:02 UTC 2025

Copy link
Contributor

@boruszak boruszak left a comment

Choose a reason for hiding this comment

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

All style suggestions. Fabulous. Splendid. Approved.

should be aware of.
<!--
Please describe why you're making this change and point out any important details the reviewers
should be aware of. A robust description helps the tech writer create a fabulous release note.
Copy link
Contributor

Choose a reason for hiding this comment

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

I love "fabulous" here! As in its Latin root: A release note to be celebrated in fable.

<!--
Please describe why you're making this change and point out any important details the reviewers
should be aware of. A robust description helps the tech writer create a fabulous release note.
If your code PR has a splendid description, link to the code PR in the links section so that
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
If your code PR has a splendid description, link to the code PR in the links section so that
If your PR updates code in the `hashicorp/nomad` repo, link to the code PR in the links section so that

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm seeing engineers creating robust descriptions in the code PR and then no description in the docs PR. In those cases, I've been copying the relevant parts of the code PR description into the docs PR description so that I don't have to constantly switch repos to see that the docs PR covers.

Comment on lines +55 to +56
**Please link to the related Nomad repo code PR!** if there is one.
The tech writer does look at the code PR description, Jira ticket, and/or GH issue before reviewing docs content.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
**Please link to the related Nomad repo code PR!** if there is one.
The tech writer does look at the code PR description, Jira ticket, and/or GH issue before reviewing docs content.
**Please link to related code PRs in the `hashicorp/nomad` repo!**
The tech writer looks at related descriptions, Jira tickets, and GH issues so
that they have the full context for the documentationupdates.

Comment on lines +58 to +59
Include links to GitHub issues, documentation, or similar which is relevant to this PR. If
this is a docs bug fix, please ensure related issues are linked so they will close when this PR is
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Include links to GitHub issues, documentation, or similar which is relevant to this PR. If
this is a docs bug fix, please ensure related issues are linked so they will close when this PR is
Include links to GitHub issues, existing documentation, and other content relevant to this PR. If
this PR implements a docs bug fix, please ensure related JIRA issues are linked so they will close when this PR is

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Only GH issues close when the PR is merged. Jira issues do not.

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