For example, refs/tags/build-\(?.\*\) will match refs/tags/build-123 and its name will be shortened to 123.
You may add a named regex capturing group called name to further customize the name extraction. For example, refs/tags/build-.\* will match a tag refs/tags/build-123 and its name will be shortened to build-123. For a matching ref, its name will be shortened to the last path-segment \('\\/'\). Patterns will be matched against the full ref-name, including the refs-prefix. For example, refs/tags/build-\(?.\*\) will match refs/tags/build-123 and its name will be shortened to 123."=\(dlgSgPreferences|dlgSgRepositorySettings).ttpGroupPatterns"Patterns will be matched against the full ref-name, including the refs-prefix. Now, once again they will be assigned to matching groups, possibly replacing other refs or possibly becoming replaced by more recent refs. Next, the refs remaining in the group will be passed on from child to parent commit. Now, once again they will be assigned to matching groups, possibly replacing other refs or possibly becoming replaced by more recent refs."=\ (dlgSgPreferences|dlgSgRepositorySettings).ttpGroupPatterns"Next, the refs remaining in the group will be passed on from child to parent commit. Optionally, enter regular expressions defining additional refs to preserve. (dlgSgPreferences|dlgSgRepositorySettings).lbl"Optionally, enter regular expressions defining additional refs to preserve."=\ Example: `refs\\/tags\\/build\(?.\\\*\)`"=\Įnter regular expressions defining the grouping. (dlgSgPreferences|dlgSgRepositorySettings).lbl"Enter regular expressions defining the grouping.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |