Skip to content
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

Merged
merged 9 commits into from
Apr 10, 2018
Merged

Started work on issue and PR templates #374

merged 9 commits into from
Apr 10, 2018

Conversation

petr-tik
Copy link
Member

@petr-tik petr-tik commented Apr 8, 2018

As explained in #373, a PR template doesn't exist and an issue template needs to be decided on

Please review and suggest changes


#### Where should the reviewer start?

#### Ideas that were considered and discarded
Copy link
Collaborator

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].

Copy link
Member

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.

@@ -0,0 +1,7 @@
#### What does this PR do?

#### Where should the reviewer start?
Copy link
Collaborator

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].

Copy link
Member

Choose a reason for hiding this comment

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

Agreed.

@@ -0,0 +1,7 @@
#### What does this PR do?
Copy link
Collaborator

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.


#### Ideas that were considered and discarded

#### Relevant tickets
Copy link
Collaborator

@jbcoe jbcoe Apr 8, 2018

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

Copy link
Member

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.

Copy link
Collaborator

@jbcoe jbcoe left a 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 jbcoe requested review from ajbennieston and Twon April 8, 2018 22:09
@petr-tik
Copy link
Member Author

petr-tik commented Apr 8, 2018

@jbcoe thanks for the review - happy to wait for the feedback from the others and add/change tomorrow

Copy link
Member

@ajbennieston ajbennieston left a 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.

petr-tik and others added 3 commits April 9, 2018 23:31
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
@ajbennieston
Copy link
Member

Looks good to me. @Twon: any comments?

@Twon
Copy link
Collaborator

Twon commented Apr 10, 2018

Yep, that looks good to me too. Go for it.

@jbcoe jbcoe merged commit c717283 into master Apr 10, 2018
@ajbennieston ajbennieston deleted the add_pr_template branch April 12, 2018 08:14
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