trac, but it is harder to construct the regex. Example: ssue(?:s)? #?(\d+) This method is required by a few issue trackers, e.g. If only one expression is set, then the bare bug IDs must be matched in the groups of the regex string. Finally there is a mandatory “ #” and a mandatory decimal number. This is followed by one or more groups each having zero or more leading whitespace, an optional comma or “ and” and more optional space. This is optionally followed by an “ s” (more than one issue) and optionally a colon. The second regex extracts plain decimal numbers from the output of the first regex, so it will return “ 23”, “ 24” and “ 25” to use as bug IDs.īreaking the first regex down a little, it must start with the word “ issue”, possibly capitalised. The first expression picks out “ issues #23, #24 and #25” from the surrounding log message. If you want to catch bug IDs as used in the expression above inside a log message, you could use the following regex strings, which are the ones used by the TortoiseGit project: ssues?:?(\s*(,|and)?\s*#\d+)+ and (\d+) you might fix several bugs and include a string something like this: “ This change resolves issues #23, #24 and #25”
This allows you to use a list of bug IDs and natural language expressions if you wish. The second expression then extracts the bare bug IDs from the result of the first regex. If two expressions are set, then the first expression is used as a pre-filter to find expressions which contain bug IDs. It contains either a single regular expressions, or two regular expressions separated by a newline. This configuration activates the bug tracking system in Regex mode. An exception is the comma, so you can comma separate several numbers. If set to true only numbers are allowed in the issue-number text field. Keep in mind though that the window will not be resized to fit this label, so keep the size of the label below 20-25 characters. If it's not set, Bug-ID / Issue-Nr: will be displayed. This text is shown by TortoiseGit on the commit dialog to label the edit box where you enter the issue number. If not defined, true is assumed, so that existing projects don't break. This configuration defines if the bug-ID is appended (true) to the end of the log message or inserted (false) at the start of the log message. As an example you might use Issue : %BUGID%, but this depends on your Tool. This ensures that your commit log contains a reference to the issue number which is always in a consistent format and can be parsed by your bug tracking tool to associate the issue number with a particular commit. It must contain %BUGID%, which is replaced with the issue number on commit. It's used to add a line at the end of the log message. If this configuration is set, then TortoiseGit will prompt you to enter an issue number when you commit your changes. This configuration activates the bug tracking system in Input field mode.
0 kommentar(er)
