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.

Sign up for GitHub

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

Jump to bottom

Add PR templates for atmospheric_physics #115

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Add PR templates for atmospheric_physics #115

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
deb114e
add PR templates
peverwhee Aug 30, 2024
c63386f
add default template
peverwhee Aug 30, 2024
0ce6e39
Update develop-template.md
peverwhee Sep 4, 2024
18a0ff3
Update main-template.md
peverwhee Sep 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/develop-template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
Originator(s):

Summary (include the keyword ['closes', 'fixes', 'resolves'] and issue number):

Copy link
Collaborator

Choose a reason for hiding this comment

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

Perhaps add a bullet like: Purpose of PR (new scheme, modification to existing scheme, bug fix to scheme, etc.). This might be unnecessary if the PR title covers this, but if it doesn't, perhaps this information would be useful?

Copy link
Collaborator

Choose a reason for hiding this comment

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

For this section (summary and purpose), would it make sense to follow a layout similar to a few other open sourced projects (ex. dotnet/aspnetcore#55968), where we have Summary, Description and then a section for fixes/resolutions, followed by the other sections below?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Also, I think we can remove the summary line in general because the top line in the commit message will be the PR title (as seen from my last PR into the develop branch):
image

Describe any changes made to the namelist:

List all files eliminated and why:

List all files added and what they do:

List all existing files that have been modified, and describe the changes:
(Helpful git command: `git diff --name-status development...<your_branch_name>`)

Copy link
Collaborator

Choose a reason for hiding this comment

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

Add additional bullet like List how this code was validated with the new/modified features - i.e. How does the developer know that it is doing the proper thing?

List any test failures:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Perhaps specify what tests we expect to be run: List any regression test failures on xxx/yyy (where xxx/yyy is each computer/compiler). I think it is just one combo right now, but perhaps that might change?

Are there other tests we currently expect developers to run?


Is this a science-changing update? New physics package, algorithm change, tuning changes, etc?
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would suggest the bullet should be something like: Is this an answer changing PR? If so, is it a new physics package, algorithm change, tuning changes, etc?

6 changes: 6 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/main-template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
Tag name (The PR title should also include the tag name):
Originator(s):

List all `develop` PR URLs included in this PR and a short description of each:

List all test failures:
4 changes: 4 additions & 0 deletions .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
Please go the the `Preview` tab and select the appropriate PR template:

* [Develop branch](?expand=1&template=develop-template.md)
* [Main branch](?expand=1&template=main-template.md)