-
Notifications
You must be signed in to change notification settings - Fork 7
/
Copy pathdefault-config.yml
84 lines (79 loc) · 3.39 KB
/
default-config.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
#============================= SHERPA CONFIG ==================================#
# #
# This is the default configuration file for Sherpa. These values will be #
# set if no other configuration override those values. You can override #
# the values by setting them in your `$HOME/.config/sherpa/config.yml` file. #
# #
#==============================================================================#
# Sherpa issue types ----------------------------------------------------------#
# You can use the following issue types in the sections below that indicate it.
# - bugfix
# - dependency
# - deprecation
# - documentation
# - feature
# - hotfix
# - improvement
# - internal
# - refactoring
# - release
# - removal
# - revert
# - security
#-----------------------------------------------------------------------------#
# Jira configuration ---------------------------------------------------------#
jira:
# Jira authentication configuration
auth:
# The URL to connect to your Jira instance.
host: ""
# This token will be used to authenticate to Jira.
# You can generate a PAT in your Jira instance if you didn't already
# have one generated by GH Sherpa.
token: ""
# Enable this setting to skip TLS verification.
# This is useful when you are using self-signed certificates
# or when you are authenticating to a non-HTTPS Jira instance.
# WARNING: It is not recommended to enable this option unless
# you are in a trusted network.
skip_tls_verify: false
# Jira issue types configuration
# You can find the issue types ID in your Jira instance by navigating to
# https://{your-jira-domain}/jira/rest/api/2/issuetype. More info in
# https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-types/#api-group-issue-types
issue_types:
bugfix: ["1"]
feature: ["3", "5"]
improvement: ["4"]
# You can map here other issue types.
# GitHub configuration -------------------------------------------------------#
github:
# GitHub issue labels configuration
# Here you can configure the issue labels mapping between GitHub issues and
# Sherpa issue types.
issue_labels:
bugfix: ["kind/bug"]
dependency: ["kind/dependency"]
documentation: ["kind/documentation"]
feature: ["kind/feature"]
improvement: ["kind/improvement"]
internal: ["kind/internal"]
refactoring: ["kind/refactoring"]
# You can map here other issue types.
# Branches configuration -----------------------------------------------------#
branches:
# Branch prefixes configuration
# Here you can set the prefixes that will be used when creating the branches
# for the issues. By default it will use the issue type as prefix.
prefixes:
# We provide some examples below to help you configure your prefixes, select one
# issue type and map it to a custom prefix.
# Example: map `bugfix` type to a branch prefix `myfix/xxxx`:
# bugfix: myfix
# Example: map `feature` type to a branch prefix `feat/xxxx`:
# feature: feat
# Branch name max number of characters
# Useful when you want to crop the branch name to a specific length.
# By default it will use 63 for Kubernetes resources compatibility.
# You can disable this limit of characters by setting this value to 0.
max_length: 63