Globally configure the branch explorer
Globally configure branch explorer settings.
読み終わるまでの所要時間 1 分最終更新 2日前
Configure the branch explorer and use global configuration so that all clients have the same settings by default.
- In the Unity DevOps Version Control application, set your Branch Explorer configuration preferences:
- Select the Branch Explorer tab.
- Select Options to open the configuration panel and edit to your preference.
- 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
- Windows:
- Paste the file into the global configuration repository under the folder.
allrepos
Global branchexplorer.conf
file example
Refer to the following example of a global branchexplorer.confbranchexplorer.conf[Default]filters.conditional.numrules=1filters.conditional.rule0.branches_query=attribute = 'status' and attrvalue = 'RESOLVED'filters.conditional.rule0.description=Unresolved branchesfilters.conditional.rule0.enabled=truefilters.conditional.rule0.related.branches=Nonefilters.conditional.rule0.type=exclusion_rule
注
The first rule is .
rule0branchexplorer.confThe GUI combines the global and local filters. The following example shows the resulting configuration for filters:[Default]display.attributes.visible=truedisplay.changestats.visible=truedisplay.extension.visible=truedisplay.navigator.visible=falsedisplay.options.branch_level_filter=-1display.options.changeset_color=1display.options.dag_mergelinks=falsedisplay.options.draw_branches=truedisplay.options.draw_crossbranch_changeset_links=truedisplay.options.draw_labels=truedisplay.options.draw_merge_links=truedisplay.options.draw_only_relevant_changesets=falsedisplay.options.draw_taskinfo=truedisplay.options.end_date=0display.options.end_date_enablement=falsedisplay.options.full_branch_names=truedisplay.options.layout_mode=0display.options.show_parent_to_child_arrows=falsedisplay.options.start_date=636136983268496003display.options.visible=falsedisplay.properties.legend=falsedisplay.properties.visible=truedisplay.properties.zoom=0,9999999filters.conditional.numrules=1filters.conditional.rule0.branches_query=filters.conditional.rule0.color=0,128,192filters.conditional.rule0.description=Unresolved branchesfilters.conditional.rule0.enabled=truefilters.conditional.rule0.related.branches=Nonefilters.conditional.rule0.type=non_integrated_branchesfilters.conditional.visible=true
As a result of the combined rules in the example above:filters.conditional.numrules=2filters.conditional.rule0.branches_query=attribute = 'status' and attrvalue = 'RESOLVED'filters.conditional.rule0.description=Unresolved branchesfilters.conditional.rule0.enabled=truefilters.conditional.rule0.related.branches=Nonefilters.conditional.rule0.type=exclusion_rulefilters.conditional.rule1.branches_query=filters.conditional.rule1.color=0,128,192filters.conditional.rule1.description=Unresolved branchesfilters.conditional.rule1.enabled=truefilters.conditional.rule1.related.branches=Nonefilters.conditional.rule1.type=non_integrated_branches
- The combined filters don't show branches if the attribute is set to
status(because the rule type is anRESOLVEDin the global configuration).exclusion_rule - The combined filters show the branches that aren't merged (because of the rule , colored blue (RGB 0,128,192), in local configuration).
non_integrated_branches