3 ms·
“ every little change in requirements and docs has its own commit” I think this would be a great thing to have and know who changed what and when. It seems it’
by vjvjvjvjghv 1mo ago
“ every little change in requirements and docs has its own commit”
I think this would be a great thing to have and know who changed what and when. It seems it’s more of a problem of the tools being able to help the user see only what he needs to see in a certain context.
- ammar_az 1mo agoIt's a great thing if those changes live in their own repo and not mixed with changes to the code itself. Actually Jira has been doing that for a while now by offering the history view with a timeline for each change, also GitHub shows edit version for files as well. The main role for projects management is handle the chaotic way of humans communication across different organization without developer being involved in that messy cycle. But having everything in the same repo will remove this decoupling and will let developers get involved in that chaos as it's part of the repo history.