... | ... | @@ -69,21 +69,28 @@ or |
|
|
<details><summary>8. Push branch to GitHub fork</summary>
|
|
|
|
|
|
<p>
|
|
|
|
|
|
* git checkout <my_branch_name>
|
|
|
* git push origin <my_branch_name>
|
|
|
</p>
|
|
|
|
|
|
</details>
|
|
|
|
|
|
<details><summary>9. Create pull request on GitHub</summary>
|
|
|
|
|
|
<p>
|
|
|
...
|
|
|
|
|
|
The standard [GitHub pull request process](https://help.github.com/articles/creating-a-pull-request-from-a-fork/) can be used to submit a Trilinos pull request. Note that the pull request must be submitted against the <b>develop</b> branch of the trilinos/Trilinos GitHub repository, or the Trilinos Autotester will not process the pull request.
|
|
|
|
|
|
See the [Trilinos Pull Request Testing page](https://github.com/trilinos/Trilinos/wiki/Pull-Request-Testing-Interface) for information about a few special labels that can be applied to pull requests to achieve desired behavior and for a general overview of the Trilinos pull request testing capability.
|
|
|
</p>
|
|
|
</details>
|
|
|
|
|
|
<details><summary>10. Delete branch after the pull request has been merged</summary>
|
|
|
|
|
|
<p>
|
|
|
|
|
|
* git push --delete origin branchname
|
|
|
|
|
|
</p>
|
|
|
</details> |