-
Notifications
You must be signed in to change notification settings - Fork 1
/
Capefile
48 lines (39 loc) · 1.57 KB
/
Capefile
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
# Capefile is a settings file for Caperoma (programming automation system).
# More detailed information about Caperoma can be found on these sites:
# http://caperoma.io
# https://github.com/zoopyserg/caperoma/
# https://rubygems.org/gems/caperoma
# http://www.rubydoc.info/gems/caperoma/4.0.1
# This file is formatted as a YAML document.
# A working example of this configuration file in a live project can be seen here:
# https://github.com/zoopyserg/caperoma/blob/master/Capefile
# --- GITHUB SETTINGS:
## The relative path to the repository of this project on Github, to which you need to send pull requests.
github_repo: zoopyserg/caperoma
# --- JIRA SETTINGS:
## The full URL of your Jira server where you will create tasks.
jira_url: https://sergevinogradoff.atlassian.net/
## The ID of this project on your Jira system.
jira_project_id: 10001
## Issue identifiers of various types on your Jira system.
jira_issue_type_ids:
feature: 10001
bug: 10004
chore: 10001
fix: 10001
meeting: 10001
## Jira conversion identifiers.
jira_transition_ids:
todo: 11
in_progress: 21
done: 31
# --- PIVOTAL TRAKCER SETTINGS:
## The ID of this project on the PivotalTracker site.
pivotal_tracker_project_id: 2374972
## What tasks to create in PivotalTracker in case the task from Pivotal is not attached to the task in Caperoma
## (i.e. the -p or --pivotal_id parameter was not specified at the time of the task start).
create_features_in_pivotal: true
create_bugs_in_pivotal: true
create_chores_in_pivotal: true
create_fixes_in_pivotal_as_chores: false
create_meetings_in_pivotal_as_chores: false