-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Started work on issue and PR templates #374
Conversation
docs/pull_request_template.md
Outdated
|
||
#### Where should the reviewer start? | ||
|
||
#### Ideas that were considered and discarded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd tag this as [optional]
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe
#### Rationale / Background / Ideas considered and rejected [optional]
And perhaps a
#### Possible future work [optional]
Which would allow PR submitters to suggest follow-on work, which we could raise tickets for after appropriate discussion.
docs/pull_request_template.md
Outdated
@@ -0,0 +1,7 @@ | |||
#### What does this PR do? | |||
|
|||
#### Where should the reviewer start? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd tag this as [optional]
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed.
docs/pull_request_template.md
Outdated
@@ -0,0 +1,7 @@ | |||
#### What does this PR do? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like standardising existing practice so is definitely good.
docs/pull_request_template.md
Outdated
|
||
#### Ideas that were considered and discarded | ||
|
||
#### Relevant tickets |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely needed. I often forget this bit.
Probably worth adding
#### Closes [TicketNumbers]
too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely add the closes [ticketnumbers]
part! I forget that too often.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll leave this to Ant to review as he's probably going to find it the most useful.
@jbcoe thanks for the review - happy to wait for the feedback from the others and add/change tomorrow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with suggested changes.
Following the review: sectioons for What does it do and what ticket it closes are universal. The rest are optional. Reduced the level of md headings
Looks good to me. @Twon: any comments? |
Yep, that looks good to me too. Go for it. |
As explained in #373, a PR template doesn't exist and an issue template needs to be decided on
Please review and suggest changes