This repository was archived by the owner on Aug 13, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathv1git.conf.example
More file actions
46 lines (41 loc) · 1.95 KB
/
v1git.conf.example
File metadata and controls
46 lines (41 loc) · 1.95 KB
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
v1config:
# The following is taken from the url of your v1 instance
# eg. https://www14.v1host.com/v1sdktesting/Default.aspx
hostname: 'www14.v1host.com'
instance: 'v1sdktesting'
# we can either use username/password or access_token - access_token is preferred
#username: ''
#password: ''
# You can get the access_token by mousing over your name in the upper-right
# corner of v1 and clicking "Applications". A dialog will walk you through
# generating an access_token.
access_token: ''
# probably do not need to change this.
type_prefixes:
D: 'Defect'
B: 'Story'
port: 443
protocol: 'https'
v1_story_statuses:
# go to #{YOURHOST}/rest-1.v1/Data/StoryStatus ie.
# https://www14.v1host.com/v1sdktesting/rest-1.v1/Data/StoryStatus
# to find the story status IDs for your v1 account.
# 'test' status probably won't be setup by default in your versionone
# account. You may need to have to add a column in kanban:
# https://community.versionone.com/Help-Center/Portfolio_Planning/Portfolio_Kanban/Working_with_Portfolio_Kanbans#Changing_Columns
# https://community.versionone.com/Help-Center/Setup_and_Administration/List_Type_Administration
# Story Status to set when running `v1git develop`
develop: 'StoryStatus:134' # In Progress
# Story status to set when running `v1git qa`
test: 'StoryStatus:1073' # In Test
github:
# If you're using github enterprise, point this to your domain name
# Typically, you'll need to add /api/v3 to it. Eg.
# https://github.mydomain.com/api/v3/
endpoint: https://api.github.com
# Auth token used to access github. Leave this as "AUTOGENERATE" to have v1git create one for you. The auth token
# needs to have permission to read/write code in repos
# if you use 2FA, you will need to generate the auth_token yourself. Please follow
# https://help.github.com/articles/creating-an-access-token-for-command-line-use/
# make sure to check "repo" permissions
oauth_token: "AUTOGENERATE"