There’s a community standard out there called Conventional Commit for structured git-commit messages. If you don’t know about it already, it recommends a strict type(scope?): description format for describing a code change in a repo.
One thing I’ve found useful with some git forges (haven’t tried them all so no idea if it’s universal) is tagging commits to issues and/or prs. Never bothered with the auto close functionality but assuming people actually put details into tickets, it’s come in handy a bunch of times this year to figure out why something got implemented when the original contributor is long gone.
One thing I’ve found useful with some git forges (haven’t tried them all so no idea if it’s universal) is tagging commits to issues and/or prs. Never bothered with the auto close functionality but assuming people actually put details into tickets, it’s come in handy a bunch of times this year to figure out why something got implemented when the original contributor is long gone.