Skip to content

Conversation

@daniel-eckel
Copy link
Collaborator

One line description of your change (less than 72 characters)

Problem

Explain the context and why you're making that change. What is the problem
you're trying to solve? In some cases there is not a problem and this can be
thought of being the motivation for your change.

Solution

Describe the modifications you've done.

Result

What will change as a result of your pull request? Note that sometimes this
section is unnecessary because it is self-explanatory based on the solution.

Some important notes regarding the summary line:

  • Describe what was done; not the result
  • Use the active voice
  • Use the present tense
  • Capitalize properly
  • Do not end in a period — this is a title/subject
  • Prefix the subject with its scope

Test Plan

(Write your test plan here. If you changed any code, please provide us with
clear instructions on how you verified your changes work.)

@shaselton-usds
Copy link
Collaborator

@daniel-eckel Looks good - might want to keep an eye on the auto-generated text though ;).

@shaselton-usds shaselton-usds merged commit 0ed86e0 into main Dec 2, 2025
5 checks passed
@shaselton-usds shaselton-usds deleted the daniel-eckel-data-dictionary-link branch December 2, 2025 20:31
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.

4 participants