You may want to look at the `git notes` functionality that keeps local notes for commits. Probably a bit of a rabbit hole initially (i.e. documentation `git help notes` could be better, but maybe https://github.blog/2010-08-25-git-notes-display/), but others use them successfully.
Philip On Wednesday, August 5, 2020 at 3:35:00 AM UTC+1, SJW wrote: > > I am trying to find a good way to track changes to the db but havn't got > it down pat yet. > > What I am doing > > ``` > git branch feature > git checkout feature > ``` > > modify code and add/modify database tables > ... > create a txt file called feature.txt and list changes. e.g. DB ALTER > statements etc. that I need to apply to staging and production db's > ... > > ``` > git add . > git commit -m "Message" > git checkout staging > git merge feature > git checkout master > git merge feature > ``` > > Problem I have is that I have all these txt files that are just notes so I > delete them but they keep reappearing ( because I merged them into master > and then create new branch etc. ) > > I found this was a bit annoying so I stopped adding and committing the txt > files but now I have these txt files sitting in the unstaged changes area > of all projects - not a great idea either. > > Any suggestions on how to better manage these notes and somehow ensure > they remain linked to each feature branch? > > Thanks > > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/7b03a47a-ac13-410f-81f8-45806da942f5o%40googlegroups.com.
