Earlier quoted context omitted.
I set a breakpoint and run the test suite for that answer
So you never need to understand when or why a bug was introduced? Or you never need to understand why the current behavior as is it is?
Git log is not a changelog
71–80 of 92 posts
Re: Git log is not a changelog
#72Use multiple "-m" parameters in your git commit. git commit -m "feat: script pretty print" -m "added variables for bold, normal, and a nice blue arrow" becomes: feat: script pretty print added variables for bold, normal, and a nice blue arrow In your git log output. Use extra "-m" sections for stuff like ticket references, or other relevant information like a link to a design document.
Alternatively just avoid the `-m` flag and open the message in `$EDITOR`
Re: Git log is not a changelog
#73Earlier quoted context omitted.
You didn't answer why. My code passes all the unit test and we almost always have real code using it immediately. The function works. Why am I reading it? The only thing I read are bug reports (usually a spec problem, not normally a logic bug) and new features, or test outputs
If someone complains that our system did something weird, sometimes it’s a mistake we can just fix, but sometimes it’s a non-obvious consequence of some requirement (which I might not have been aware of) that we have to explain to our consumer. It also helps a lot to tell whether it has been like that for a week or five years. I can’t even imaging having a spec that fully answers anything like this; Microsoft tried f…
Re: Git log is not a changelog
#74Re: Git log is not a changelog
#75Yes the Git log is the ChangeLog. For instance, I retired the ChangeLog in the TXR project in 2015; commit messages continue to be in the ChangeLog format. A ChangeLog file could easily be produced from the commit messages. Replicating that information in a file that is checked into git is silly; you're just begging for merge conflicts. Any time anyone sends you a patch, if it is not rebased to your current HEAD, you…
(Author here) Yes, "release notes" is probably the appropriate term. The issue remains however: many projects generate their release notes from their git commit messages. Regarding the conflicts issue, this is where tools like Changie can help: instead of modifying one single file, every merge adds its own separated entry. They are then assembled together at release time with `changie batch $VERSION` to produce a sin…
If "every merge adds its own separated entry" and that doesn't refer to a special section of the commit message, you're doing something silly.
Re: Git log is not a changelog
#76Re: Git log is not a changelog
#77Earlier quoted context omitted.
We autogenerate our CHANGELOG.md extract from Changelog-[section] our git commit messages (Release Captain massages them if necessary), and have a GH bot which checks that you have a Changelog- note somewhere in your PR commits (can be Changelog-None: ....). This avoid merge hell on the CHANGELOG.md file.
Setting `CHANGELOG.md merge=union` in .gitattributes mostly eliminates spurious merges conflicts on the changelog.
Re: Git log is not a changelog
#78Earlier quoted context omitted.
I set a breakpoint and run the test suite for that answer
Quoted post unavailable.
https://news.ycombinator.com/item?id=32104697
https://news.ycombinator.com/item?id=32086054
https://news.ycombinator.com/item?id=32085905
https://news.ycombinator.com/item?id=32085736
We eventually ban accounts that carry on like this on HN. I don't want to ban you, so if you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here, we'd appreciate it.
Re: Git log is not a changelog
#79Earlier quoted context omitted.
Quoted post unavailable.
Could you please stop breaking the site guidelines? You've been doing it a lot lately, unfortunately. Not just with these off-topic complaints about downvoting, but with comments like these: https://news.ycombinator.com/item?id=32104697 https://news.ycombinator.com/item?id=32086054 https://news.ycombinator.com/item?id=32085905 https://news.ycombinator.com/item?id=32085736 We eventually ban accounts that carry on like…
For example (one that you linked to) a person said I was wrong and his comment wasn't flagged yet when I asked him to stop replying to my comments (many of my comments in the thread weren't on his comments) mine gets flagged https://news.ycombinator.com/item?id=32086054
Re: Git log is not a changelog
#80Earlier quoted context omitted.
Could you please stop breaking the site guidelines? You've been doing it a lot lately, unfortunately. Not just with these off-topic complaints about downvoting, but with comments like these: https://news.ycombinator.com/item?id=32104697 https://news.ycombinator.com/item?id=32086054 https://news.ycombinator.com/item?id=32085905 https://news.ycombinator.com/item?id=32085736 We eventually ban accounts that carry on like…
Some of those comments were in response to people calling me a liar with upvotes on their comments and downvotes on mine. It's incredibly irritating and frustrating when it appears those accusing me of lying not suffer any consequences. For example (one that you linked to) a person said I was wrong and his comment wasn't flagged yet when I asked him to stop replying to my comments (many of my comments in the thread w…
If you see a post that ought to have been moderated but hasn't been, the likeliest explanation is that we didn't see it. (There are far too many posts here for us to read them all.) You can help by flagging it or emailing us at hn@ycombinator.com.
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...