Changes between Version 1 and Version 2 of DevNotes/DevGuide/CommitMessage


Ignore:
Timestamp:
Apr 1, 2019 6:52:43 AM (5 years ago)
Author:
butler
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • DevNotes/DevGuide/CommitMessage

    v1 v2  
    33Issues being addressed by a commit or pull request should be referred to in that commit or pull request. Most often you will be closing the issue with the pull request.  To do so use one of the magic words below in the commit message or the pull request. 
    44 
    5 To refer to issues in commit messages simply type the issue ref such as #10. In order to have the issue be closed whenever the change is merged into master, the syntax is of the form [command] [issueno]. A colon between the command and the issue reference is allowed as is capitalization of the command.  The allowed commands are given below: 
     5To refer to issues in commit messages simply type the issue ref. In order to have the issue be closed whenever the change is merged into master, the syntax is of the form [command] [issueno]. A colon between the command and the issue reference is allowed as is capitalization of the command.  The allowed commands are given below: 
    66 
    77{{{ 
     
    2323}}} 
    2424 
     25**NOTE2**: to reference an issue within the current repository [issueno] is just #issueno.  To reference an issue in another repository however [issueno] is username/repository#issueno. for example to reference a sasview issue from a sasview commit use `#10`. To reference a sasmodels issue in a sasview commit use `SasView/sasmodels#10` 
     26 
    2527The full documentation is available on github: ​​https://help.github.com/en/articles/closing-issues-using-keywords 
    2628