-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathconfig-template.yaml
158 lines (112 loc) · 5.35 KB
/
config-template.yaml
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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
# The username of the assignees to be added on the pull request.
assignees:
- example
# Email of the committer. If not set, the global git config setting will be used.
author-email:
# Name of the committer. If not set, the global git config setting will be used.
author-name:
# The branch which the changes will be based on.
base-branch:
# Base URL of the target platform, needs to be changed for GitHub enterprise, a self-hosted GitLab instance, Gitea or BitBucket.
base-url:
# The name of the branch where changes are committed.
branch: multi-gitter-branch
# Use a code search to find a set of repositories to target (GitHub only). Repeated results from a given repository will be ignored, forks are NOT included by default (use `fork:true` to include them). See the GitHub documentation for full syntax: https://docs.github.com/en/search-github/searching-on-github/searching-code.
code-search:
# The commit message. Will default to title + body if none is set.
commit-message:
# The maximum number of concurrent runs.
concurrent: 1
# What should happen if the branch already exist.
# Available values:
# skip: Skip making any changes to the existing branch and do not create a new pull request.
# replace: Replace the existing content of the branch by force pushing any new changes, then reuse any existing pull request, or create a new one if none exist.
conflict-strategy: skip
# Create pull request(s) as draft.
draft: false
# Run without pushing changes or creating pull requests.
dry-run: false
# Limit fetching to the specified number of commits. Set to 0 for no limit.
fetch-depth: 1
# Fork the repository instead of creating a new branch on the same owner.
fork: false
# If set, make the fork to the defined value. Default behavior is for the fork to be on the logged in user.
fork-owner:
# The type of git implementation to use.
# Available values:
# go: Uses go-git, a Go native implementation of git. This is compiled with the multi-gitter binary, and no extra dependencies are needed.
# cmd: Calls out to the git command. This requires git to be installed and available with by calling "git".
git-type: go
# The name of a GitLab organization. All repositories in that group will be used.
group:
- example
# Include GitLab subgroups when using the --group flag.
include-subgroups: false
# Insecure controls whether a client verifies the server certificate chain and host name. Used only for Bitbucket server.
insecure: false
# Take manual decision before committing any change. Requires git to be installed.
interactive: false
# Labels to be added to any created pull request.
labels:
- example
# The file where all logs should be printed to. "-" means stdout.
log-file: "-"
# The formatting of the logs. Available values: text, json, json-pretty.
log-format: text
# The level of logging that should be made. Available values: trace, debug, info, error.
log-level: info
# If this value is set, reviewers will be randomized.
max-reviewers: 0
# If this value is set, team reviewers will be randomized
max-team-reviewers: 0
# The name of a GitHub organization. All repositories in that organization will be used.
org:
- example
# The file that the output of the script should be outputted to. "-" means stdout.
output: "-"
# Don't use any terminal formatting when printing the output.
plain-output: false
# The platform that is used. Available values: github, gitlab, gitea, bitbucket_server.
platform: github
# The body of the commit message. Will default to everything but the first line of the commit message if none is set.
pr-body:
# The title of the PR. Will default to the first line of the commit message if none is set.
pr-title:
# The name, including owner of a GitLab project in the format "ownerName/repoName".
project:
- group/project
# The name, including owner of a GitHub repository in the format "ownerName/repoName".
repo:
- my-org/js-repo
- other-org/python-repo
# Exclude repositories that match with a given Regular Expression
repo-exclude:
# Include repositories that match with a given Regular Expression
repo-include:
# Use a repository search to find repositories to target (GitHub only). Forks are NOT included by default, use `fork:true` to include them. See the GitHub documentation for full syntax: https://docs.github.com/en/search-github/searching-on-github/searching-for-repositories.
repo-search:
# The username of the reviewers to be added on the pull request.
reviewers:
- example
# Skip repositories which are forks.
skip-forks: false
# Skip pull request and directly push to the branch.
skip-pr: false
# Skip changes on specified repositories, the name is including the owner of repository in the format "ownerName/repoName".
skip-repo:
- example
# Use SSH cloning URL instead of HTTPS + token. This requires that a setup with ssh keys that have access to all repos and that the server is already in known_hosts.
ssh-auth: false
# Github team names of the reviewers, in format: 'org/team'
team-reviewers:
- example
# The personal access token for the targeting platform. Can also be set using the GITHUB_TOKEN/GITLAB_TOKEN/GITEA_TOKEN/BITBUCKET_SERVER_TOKEN environment variable.
token:
# The topic of a GitHub/GitLab/Gitea repository. All repositories having at least one matching topic are targeted.
topic:
- example
# The name of a user. All repositories owned by that user will be used.
user:
- example
# The Bitbucket server username.
username: