Skip to content

Commit

Permalink
Update contributing page
Browse files Browse the repository at this point in the history
  • Loading branch information
aeslaughter committed Nov 4, 2020
1 parent b6a67b7 commit c8bf78c
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 1 deletion.
2 changes: 1 addition & 1 deletion .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
[Contributing to MOOSE](http://mooseframework.org/wiki/Contributing/)
[Contributing to MOOSE](https://mooseframework.inl.gov/framework_development/contributing.html)
10 changes: 10 additions & 0 deletions modules/doc/content/framework_development/contributing.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,16 @@ In addition: [our own slides](https://mooseframework.org/static/media/uploads/do

The main thing to remember when issuing a PR for MOOSE is that all PRs should be specified to go to the `next` branch.

## Pull Request Assignee

In most cases a PR will be assigned to MOOSE developer. The assignee is designated to help ensure
that the request is reviewed and merged (or canceled); they are not necessarily the reviewer. The aim
is to make sure every PR is being addressed and monitored. They should also serve as a point of
contact for the PR creator.

!alert note
MOOSE developers should expect to be assigned to their own PRs, as they should know who would be best to review the content.

## What Now?

The next phase is covered in [How a Patch Becomes Code](framework_development/patch_to_code.md)... that will take you through the process of a PR ultimately making it's way into the `master` branch in MOOSE...
Expand Down

0 comments on commit c8bf78c

Please sign in to comment.