My recent brush with a forgotten stash has led me to consider again an issue
which I've never really got a complete answer to - how much information (if
any) about a project should be kept outside Git.
IOW do developers keep a note (on paper, spreadsheet, database?) of how
branches inter-relate, their purpose and so on.
An example: For a website I'm currently developing, the customer has asked
me to make what is really a simple cosmetic change. I've done so on a branch
called "cola_moss". But it could be several days or even weeks before the
customer approves the change and the cola_moss branch can be merged with
master. In the meantime, other development work continues on other branches.
By the time I get back to the cola_moss branch I'll not remember what else
was happening at the time it was created.
I've found some very useful stuff on line about workflow, but it's all about
how to use Git, not how to record the process.
So do developers generally just use the information obtainable from Git
itself or do they keep external notes too; and if so, what do they look
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at