Geek asks and answers

Git branch tracking?

Possible duplicates:
How do you comment on the thread? branch descriptions in git

I have a repo with lots of branches. Maybe 12 or so, and in the near future they will not be combined into masters.

Is there a way to document the purpose of each branch inside git?

What I'm looking for is a thread that the commit message is a commit.

I don’t think that tags are what I want, because tags do not follow HEAD, as I add more commits to the branch.

I could write a plaintext file that lists the status of each branch with some notes, but it’s not obvious which branch the text file will belong to.

To clarify, I call my branches. But I would also like to have a description. So, for example, I would like to write for the branch RTPhase:

Functions have been added in this thread to support real-time curvature and phase analysis. As a compromise, it runs slower than other branches because it uses features such as calculating average curvature that were not optimized for speed.

+3
source share
3 answers

The answer I come to is to develop an agreement that I can adhere to strictly.

"" "". "" ( , ) "". "dev".

. , -, , "dev/maps". , "dev/survey".

, , , , "/ -".

, , "".

+3

, , ( :) , :

git notes add -m "this branch is for blah blah"

post-commit :

#!/bin/sh
git notes show HEAD~1
git notes copy HEAD~1 HEAD

git notes remove HEAD~1

git notes show, , . Tadaaa!:)

+1

More articles:


All Articles