Stream: committers/git-help
Topic: Change Tracking
Grahame Grieve (Oct 11 2018 at 05:10):
so I have another issue related to Git. In the good old days, I would mark the svn revision number in each task as a comment. So if you wanted to see what changes were associated with a particular task, you'd go to the task, see the svn revision, and then look that up in the log.
Grahame Grieve (Oct 11 2018 at 05:11):
what should I record in the task for git?
Lloyd McKenzie (Oct 11 2018 at 05:49):
Commit date would get you "close". Commit date + branch name should generally be unique. But that's a lot more work than the simple SVN number
Bryn Rhodes (Oct 11 2018 at 14:09):
I have been using the actual commit link, e.g. https://github.com/HL7/fhir/commit/c27b4eaede30c4537c55ae885110719ef3067ae0
Grahame Grieve (Oct 11 2018 at 16:32):
ok. well, I'm just using the format git [id] where id is the end of that url. since the rest is template. wonder if we can template it like GC#[id]?
Grahame Grieve (Oct 12 2018 at 19:12):
@Josh Mandel you know how you added the very useful GF# for gForge - can we add a similer one like GH#[id] for https://github.com/HL7/fhir/commit/[id]?
Josh Mandel (Oct 12 2018 at 19:54):
Absolutely (it's configurable in Zulip settings I think).
Grahame Grieve (Oct 12 2018 at 19:59):
hmm I didn't find it - where to look?
Grahame Grieve (Oct 12 2018 at 20:03):
found it
Grahame Grieve (Oct 12 2018 at 20:03):
GH#aaf23f528 (testing)
Josh Mandel (Oct 15 2018 at 19:10):
Interesting -- I was thinking this would refer to PRs rather than commits. We might want commit# and pr# ?
Grahame Grieve (Oct 15 2018 at 19:11):
maybe. I'm not really interested in pr# though?
Josh Mandel (Oct 15 2018 at 19:24):
OK -- well, we know how to make more shortcuts down the line if we want 'em!
Last updated: Apr 12 2022 at 19:14 UTC
