aka re: outdated responses -- blog and/or email list for when 'new/updated version' pushed out with errata/change log location.
[0] : https://blog.bitsrc.io/literate-programming-a-radical-approa...
[1] : https://blog.codacy.com/coding-standards
[2] : https://github.com/git-lfs/git-lfs/blob/main/.github/workflo...
[3] : https://github.com/git-lfs/git-lfs/blob/main/.github/workflo...
enforcing repository management policies : https://docs.github.com/en/enterprise-cloud@latest/admin/pol...
automating code formatting : https://medium.com/@sixpeteunder/automating-code-formatting-...
using git hooks to remind via email about other things on the check list that need to be updated/done per local policy (aka notice to user manual group about changes)
things to 'git' : https://www.redhat.com/sysadmin/git-hooks
managing organizational publications with git : https://docs.github.com/en/enterprise-server@3.11/organizati...
git for writers : https://www.gitkraken.com/gitkon/git-for-writers
git for blog posts : https://opensource.com/article/19/4/manage-multimedia-files-...
git for devops : https://www.atlassian.com/git/tutorials/comparing-workflows