Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 829
    • Issues 829
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #5026
Closed
Open
Created Jan 29, 2018 by Bitbucket Importer@bitbucket_importerOwner

Branch coloring: Allow wildcards in "branchcolors" setting

Created originally on Bitbucket by DerColonel (Nikolaos Gkinos)

It would be nice to have simple wildcard support for the "branchcolors" setting in the "[tortoisehg]" section.

I imagine it working like this:

#!ini
[tortoisehg]
branchcolors = default:#016450 release/*:#FE8614

As a result, "default" should be colored #016450 while "release/17", "release/17.1", "release/17.2" should be colored #FE8614.

Above snippet is just an example. I guess some kind of escaping will be necessary to realize this.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking