Prepend commits with the file or component which it is affecting.
Readme: add install instructions
In git, there are commands to see what files a commit changed - to me, prepending files names seems unnecessary
We did this at my last job as well. Either the filename or if it's multiple the source of the changes. It makes for a much easier to read git history / merge request.
I agree with the component / subsystem - the file is just a special case of that (of a very small component).
Visual Stuido Team Explorer shows them as well, but this makes sense for ones that dont!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Prepend commits with the file or component which it is affecting.
Readme: add install instructions
In git, there are commands to see what files a commit changed - to me, prepending files names seems unnecessary
We did this at my last job as well. Either the filename or if it's multiple the source of the changes. It makes for a much easier to read git history / merge request.
I agree with the component / subsystem - the file is just a special case of that (of a very small component).
Visual Stuido Team Explorer shows them as well, but this makes sense for ones that dont!