pttool 0.0.3 → 0.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +35 -2
- data/lib/pttool/helper.rb +2 -2
- data/lib/pttool/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 1098ae139e613ec441ee25b907566737cb03a0d2
|
|
4
|
+
data.tar.gz: f2bc9a7ec1b47d9cb3596a706d8472b8235b0e86
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6f9f41b3808575f0594ba11ca72cae6033dc0e7065959012e86256dcf835dcd7e03a8bc92fe5ba26e16706b65f0cd43708a1fc62d8611264b5b6ce1cac45cbc7
|
|
7
|
+
data.tar.gz: e50b0eb4a14bcdda5a5877704bf4bf036f320c758a8979a227cc95db502d42106bdd77ffb1a745e97926337f9c2ef7ed806003c1f8247654fd33dab51f3ba33f
|
data/README.md
CHANGED
|
@@ -7,15 +7,48 @@
|
|
|
7
7
|
|
|
8
8
|
## Usage
|
|
9
9
|
|
|
10
|
-
### List of PT Projects
|
|
11
|
-
|
|
12
10
|
In order to use this tool, the environment variable `PT_TOKEN` must be set to
|
|
13
11
|
your PivotalTracker API key. The key is listed under the "API TOKEN" section at
|
|
14
12
|
the bottom of your PivotalTracker
|
|
15
13
|
[profile](https://www.pivotaltracker.com/profile)."
|
|
16
14
|
|
|
15
|
+
### Obtain List of PivotalTracker Projects
|
|
16
|
+
|
|
17
17
|
pttool projects
|
|
18
18
|
|
|
19
|
+
Its output will look similar to:
|
|
20
|
+
|
|
21
|
+
1130000: Engineering Backlog
|
|
22
|
+
820000: Product Backlog
|
|
23
|
+
|
|
24
|
+
### Synchronize Users Across Projects
|
|
25
|
+
|
|
26
|
+
pttool sync "Engineering Backlog" "Product Backlog"
|
|
27
|
+
|
|
28
|
+
The above command will obtain a list of users for both of the PivotalTracker
|
|
29
|
+
projects, and then prompt you to add the missing users. Its output looks
|
|
30
|
+
similar to:
|
|
31
|
+
|
|
32
|
+
Do you want to add 28 people to Engineering Backlog? [(y)es|(N)o|(a)bort]
|
|
33
|
+
Do you want to add 34 people to Product Backlog? [(y)es|(N)o|(a)bort]
|
|
34
|
+
|
|
35
|
+
If you want to see which users are to be added try the `--dryrun` option:
|
|
36
|
+
|
|
37
|
+
pttool sync "Engineering Backlog" "Product Backlog" --dryrun
|
|
38
|
+
|
|
39
|
+
Its output looks like:
|
|
40
|
+
|
|
41
|
+
The following would become members on all projects:
|
|
42
|
+
Captain Hook (hook@never.land)
|
|
43
|
+
Peter Pan (pan@never.land)
|
|
44
|
+
Tinker Bell (tink@never.land)
|
|
45
|
+
|
|
46
|
+
New members for Engineering Backlog:
|
|
47
|
+
Tinker Bell (tink@never.land)
|
|
48
|
+
|
|
49
|
+
New members for Product Backlog:
|
|
50
|
+
Peter Pan (pan@never.land)
|
|
51
|
+
|
|
19
52
|
### Other
|
|
20
53
|
|
|
21
54
|
To see a list of all commands simply run `pttool` or `pttool --help`.
|
data/lib/pttool/helper.rb
CHANGED
|
@@ -10,8 +10,8 @@ module PTTool
|
|
|
10
10
|
%w(y yes true 1).include?(response)
|
|
11
11
|
end
|
|
12
12
|
|
|
13
|
-
def self.add_membership(project,
|
|
14
|
-
project.add_membership(person_id:
|
|
13
|
+
def self.add_membership(project, person, role = 'member')
|
|
14
|
+
project.add_membership(person_id: person.id, role: role)
|
|
15
15
|
end
|
|
16
16
|
end
|
|
17
17
|
end
|
data/lib/pttool/version.rb
CHANGED