STORY_NUM is easy to miss after author is set

[xinzweb]

Considering you already have pair setup git author alice bob, and they are working on story 1111. then they have to do the export STORY_NUM first, then do the git author to set it.

Once, they move on to the next story, they set the STORY_NUM, but then they have to do git author again to let it refreshed to the template.

Proposal

How about we just do git author alice bob #1111 to directly set the story number into the template other than depends on the STORY_NUM?

[amilkh]

+1 I like it.

[dsharp-pivotal]

If you want to do no work, you can just use it like this:

STORY_NUM='#1111 story description' git author alice bob

Alternatively, we could replace STORY_NUM with some sort of argument.

Remember the use case of having a story description in the comment below the story number.

Could use a flag:

git author ab bc -s '#1111 story description'

Or check for a leading #:

git author ab bc '#1111 story description'

[xinzweb]

Please see if the new PR https://github.com/pivotal/git-author/pull/9 of README make the usage more obvious.

Thanks a lot for the discussion.

Shin

On Thu, Apr 5, 2018 at 4:42 PM, David Sharp notifications@github.com wrote:

If you want to do no work, you can just use it like this:

STORY_NUM='#1111 story description' git author alice bob

Alternatively, we could replace STORY_NUM with some sort of argument.

Remember the use case of having a story description in the comment below the story number.

Could use a flag:

git author ab bc -s '#1111 story description'

Or check for a leading #:

git author ab bc '#1111 story description'

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pivotal/git-author/issues/8#issuecomment-379108421, or mute the thread https://github.com/notifications/unsubscribe-auth/AAsLuhIlQtcW5PyphZm8TtqZ3vJHVYzpks5tlqwCgaJpZM4S_iS5 .

-- Shin Pivotal | Sr. Principal Software Eng, Data R&D