latest 9 messages by nettlejam
+
[2015-03-26T15:41:20Z]
nettlejam
From some googling it looks like github supports keywords in commit messages, but it doesn't seem to be for what I want to do (it's for closing issues, etc).
+
[2015-03-26T15:39:52Z]
nettlejam
milki - that sounds nice, but I'm new to git and github. So it's not obvious how I would do that
+
[2015-03-26T15:31:36Z]
nettlejam
I guess maybe the solution is to agree on a special keyword to be included in commit messages, that we can search for. Seems kludgy though :(
+
[2015-03-26T15:27:18Z]
nettlejam
Hmm. gihub dropped support for git notes last year. I wonder why?
+
[2015-03-26T15:25:12Z]
nettlejam
tobiasvl: yeah, i guess I wanted a way to flag a commit that would be part of a pull request, but so that that information would not be 'forgotten' in a later pull request (say, it starts in a feature branch, is involved in a pull request into develop, but then when there's a pull request to merge develop into master, I want that info to be visible again)
+
[2015-03-26T15:20:58Z]
nettlejam
milki - thanks. Will take a look at that
+
[2015-03-26T15:19:27Z]
nettlejam
Trying this question again: Is there some git or github 'native' way to 'flag' a particular commit as you make it for later review? Like if the commit changes something about the code that should be documented? I'm new to git and my ignorant solution would be to maintain a text file somewhere else with notes, saying: watch out for commit abcdef0, it introduces a new required parameter, or something...
+
[2015-03-25T22:34:40Z]
nettlejam
Like, say I commit a change that changes some parameter required for the code to run. I want that info to be noticed in code revew and before it goes into production, etc.
+
[2015-03-25T22:34:08Z]
nettlejam
Not sure if this is a git or github or just a stupid question, but is there a way to 'flag' a certain commit so that it can show up for review later?