-
Notifications
You must be signed in to change notification settings - Fork 31
/
default.yaml
99 lines (98 loc) · 3.03 KB
/
default.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
# These are default Tachikoma's settings.
#
# The name as a committer name on git commit.
# See:
# https://github.com/sanemat/do-not-merge-wip-for-github/commit/597425a65b87e22657a69172de182f978eed4d72
# TODO: commiter is typo, committer is valid, so I'll fix this v5
#
commiter_name: 'bot-motoko'
#
# The email as a committer email on git commit.
# See:
# https://github.com/sanemat/do-not-merge-wip-for-github/commit/597425a65b87e22657a69172de182f978eed4d72
# TODO: commiter is typo, committer is valid, so I'll fix this v5
#
commiter_email: '[email protected]'
#
# The GitHub account for pull request.
# See:
# https://github.com/sanemat/do-not-merge-wip-for-github/pull/25
#
github_account: 'bot-motoko'
#
# The branch is checked out.
# e.g. $ git checkout -b new_branch [origin/master]
#
base_remote_branch: 'origin/master'
#
# The timestamp is used identifying branch/pull request
# with human readable format.
# See available format:
# http://docs.ruby-lang.org/en/2.2.0/Time.html#method-i-strftime
#
timestamp_format: '%Y%m%d%H%M%S'
#
# The pull request body contents.
# you can use text/html/markdown and any format
# which GitHub(via Octokit) accepts.
# See:
# https://github.com/sanemat/gist-mail/pull/54
#
pull_request_body: ':hamster::hamster::hamster:'
# The pull request title.
# You can change pull request title. Default is `Exec tachikoma update %s`
# %s will be setted timestamp.
#
pull_request_title: "Execute `bundle update` at %s"
#
# The base branch which you want to pull request,
# master is most popular, develop and gh-pages are common.
#
pull_request_base: 'master'
#
# The type about fork & pull and shared repository
# See also:
# https://help.github.com/articles/types-of-collaborative-development-models/
#
# Supported: 'fork', 'shared'
#
type: 'fork'
#
# The URL of git repository you want to execute.
# https is highly recommended.
#
url: 'https://example.com/git-url.git'
#
# For ruby bundler parallel install option
# Require Bundler v1.4.0 or higher
# See also:
# http://robots.thoughtbot.com/parallel-gem-installing-using-bundler
#
# Supported: 1, 2, 3, ...
#
bundler_parallel_number: 4
#
# Use shallow clone for huge repository, if you want.
# Require Git v1.9.0 or higher
# We can push from a shallowly-cloned repository above git v1.9.0
# https://github.com/git/git/blob/master/Documentation/RelNotes/1.9.0.txt
# See also:
# http://blogs.atlassian.com/2014/05/handle-big-repositories-git/
# e.g. Tachikoma.io's default is 100, Travis-CI's default is 50 :)
#
# Supported: false, 1, 2, 3, ...
#
git_clone_depth: false
#
# Bundler v1.10.0 or higher tracks Bundler version in lockfile.
# We should use latest Bundler, but sometimes we are afraid we have to use older Bundler.
# We use Different version of Bundler between a project and a local machine.
# In addition, Bundler v1.9.x removes BUNDLED WITH section.
# RestoreBundledWith solves these conflicts.
# RestoreBundledWith restores BUNDLED WITH section from git repository.
# See also:
# https://github.com/packsaddle/ruby-restore_bundled_with
#
# Supported: true, false
#
bundler_restore_bundled_with: false