git_trello_post_commit 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +4 -4
- data/lib/git_trello_post_commit/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: 471b1b00e71f8ff30557b7b4aafcfea9bff20e0b
|
4
|
+
data.tar.gz: 5259e88d12923ffc55720fb1e22c9251685fe9dd
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: e80dbf6367d3f4b5a829a3bbeb35f6176fb1a205b2ce795b21e61210e083b9d999b01c486b860552cffeccfd036a31330aab651fc5a8463ce3f2767c3f55f153
|
7
|
+
data.tar.gz: 1c4433c99c886420ef7015b9d65771b01b4bc908f9b3885a104dbf41beaf345092dfa1cf57ec51b9e84f065c6dab6b8ec6be47b5667995f0ad7fc1f545c7e2d1
|
data/README.md
CHANGED
@@ -42,7 +42,7 @@ Get your developer key from: https://trello.com/1/appKey/generate
|
|
42
42
|
|
43
43
|
### oauth_token
|
44
44
|
|
45
|
-
You need to authorize the app with `API_KEY` to access each board
|
45
|
+
You need to authorize the app with `API_KEY` to access each board separately. To do that:
|
46
46
|
|
47
47
|
https://trello.com/1/authorize?response_type=token&name=`BOARD_NAME_AS_SHOWN_IN_URL`&scope=read,write&expiration=never&key=`API_KEY`
|
48
48
|
|
@@ -56,9 +56,9 @@ While examining the JSON from the previous step, you can also grab the value of
|
|
56
56
|
|
57
57
|
### commit_url_prefix
|
58
58
|
|
59
|
-
If you have a web view of your Git repo (such as Github), you can enter the URL which, when
|
59
|
+
If you have a web view of your Git repo (such as Github), you can enter the URL which, when suffixed with the commit SHA will show the commit in question. The hook will add a link to the commit in the comment it adds to the card.
|
60
60
|
|
61
|
-
If you
|
61
|
+
If you omit the parameter, a link won't be added.
|
62
62
|
|
63
63
|
## Usage
|
64
64
|
|
@@ -70,7 +70,7 @@ So an example commit message might be:
|
|
70
70
|
|
71
71
|
Added that awesome feature closes #42
|
72
72
|
|
73
|
-
For the 'case' and 'card' keywords, the card is moved to the list with id `LIST_ID_IN_PROGRESS`, while for keywords 'close' and 'fix', the card is moved to the list with id `
|
73
|
+
For the 'case' and 'card' keywords, the card is moved to the list with id `LIST_ID_IN_PROGRESS`, while for keywords 'close' and 'fix', the card is moved to the list with id `LIST_ID_DONE` .
|
74
74
|
|
75
75
|
## Contributing
|
76
76
|
|