Skip to content

Commit 7d229a4

Browse files
committed
commit: Document how to disable updating Linear issues
1 parent 575f4d6 commit 7d229a4

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ Finds available Capistrano stages by their prefix, e.g. `geordi deploy p` will
170170
deploy production, `geordi deploy mak` will deploy a `makandra` stage if there
171171
is a file config/deploy/makandra.rb.
172172

173-
If Linear team ids are configured (see `geordi commit`'), will offer to move deployed issues to a new state.
173+
If Linear team ids are configured (see `geordi commit`), will offer to move deployed issues to a new state. Disable with "skip".
174174

175175
When your project is running Capistrano 3, deployment will use `cap deploy`
176176
instead of `cap deploy:migrations`. You can force using `deploy` by passing the

lib/geordi/commands/deploy.rb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@
2828
deploy production, `geordi deploy mak` will deploy a `makandra` stage if there
2929
is a file config/deploy/makandra.rb.
3030
31-
If Linear team ids are configured (see `geordi commit`), will offer to move deployed issues to a new state.
31+
If Linear team ids are configured (see `geordi commit`), will offer to move deployed issues to a new state. Disable with "skip".
3232
3333
When your project is running Capistrano 3, deployment will use `cap deploy`
3434
instead of `cap deploy:migrations`. You can force using `deploy` by passing the

0 commit comments

Comments
 (0)