Documentation

Support

Unity Version Control

DevOps

On-prem

Gluon

Editor plug-in

Open Unity Dashboard

Unity Version Control

Globally configure the branch explorer

Globally configure branch explorer settings.
Read time 1 minuteLast updated 12 days ago
Configure the branch explorer and use global configuration so that all clients have the same settings by default.
  1. In the Unity DevOps Version Control application, set your Branch Explorer configuration preferences:
    1. Select the Branch Explorer tab.
    2. Select Options to open the configuration panel and edit to your preference.
  2. Copy the generated configuration file in the following location:
    • Windows: 
      C:\Users\user\AppData\Local\plastic4\branchexplorer.cfg
    • Linux and macOS: 
      $HOME/.plastic4/branchexplorer.conf
  3. Paste the file into the global configuration repository under the 
    allrepos
    folder.

Global 
branchexplorer.conf
file example

Refer to the following example of a global 
branchexplorer.conf
file: 
[Default]
filters.conditional.numrules=1
filters.conditional.rule0.branches_query=attribute = 'status' and attrvalue = 'RESOLVED'
filters.conditional.rule0.description=Unresolved branches
filters.conditional.rule0.enabled=true
filters.conditional.rule0.related.branches=None
filters.conditional.rule0.type=exclusion_rule
A local 
branchexplorer.conf
contains user-specific information too: 
[Default]
display.attributes.visible=true
display.changestats.visible=true
display.extension.visible=true
display.navigator.visible=false
display.options.branch_level_filter=-1
display.options.changeset_color=1
display.options.dag_mergelinks=false
display.options.draw_branches=true
display.options.draw_crossbranch_changeset_links=true
display.options.draw_labels=true
display.options.draw_merge_links=true
display.options.draw_only_relevant_changesets=false
display.options.draw_taskinfo=true
display.options.end_date=0
display.options.end_date_enablement=false
display.options.full_branch_names=true
display.options.layout_mode=0
display.options.show_parent_to_child_arrows=false
display.options.start_date=636136983268496003
display.options.visible=false
display.properties.legend=false
display.properties.visible=true
display.properties.zoom=0,9999999
filters.conditional.numrules=1
filters.conditional.rule0.branches_query=
filters.conditional.rule0.color=0,128,192
filters.conditional.rule0.description=Unresolved branches
filters.conditional.rule0.enabled=true
filters.conditional.rule0.related.branches=None
filters.conditional.rule0.type=non_integrated_branches
filters.conditional.visible=true
The GUI combines the global and local filters. The following example shows the resulting configuration for filters: 
filters.conditional.numrules=2
filters.conditional.rule0.branches_query=attribute = 'status' and attrvalue = 'RESOLVED'
filters.conditional.rule0.description=Unresolved branches
filters.conditional.rule0.enabled=true
filters.conditional.rule0.related.branches=None
filters.conditional.rule0.type=exclusion_rule
filters.conditional.rule1.branches_query=
filters.conditional.rule1.color=0,128,192
filters.conditional.rule1.description=Unresolved branches
filters.conditional.rule1.enabled=true
filters.conditional.rule1.related.branches=None
filters.conditional.rule1.type=non_integrated_branches
As a result of the combined rules in the example above:
  • The combined filters don't show branches if the 
    status
    attribute is set to 
    RESOLVED
    (because the rule type is an 
    exclusion_rule
    in the global configuration).
  • The combined filters show the branches that aren't merged (because of the rule 
    non_integrated_branches
    , colored blue (RGB 0,128,192), in local configuration).