Either that or use git. If you fix a bug, be sure to add a good description of the bug in the commit message; then, in the future, you can just use git log --grep "<error message>" to look through the commit history and find all the relevant information, including how it was fixed back then, who did the fixing (and might therefore know more about it), when that was, etc.
Yes, your right.. Both r the good option to have but to have is the first step and the important step to maintain the documentation for errors💚😀.. Thank you for sharing your experience...
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.
Either that or use git. If you fix a bug, be sure to add a good description of the bug in the commit message; then, in the future, you can just use
git log --grep "<error message>"to look through the commit history and find all the relevant information, including how it was fixed back then, who did the fixing (and might therefore know more about it), when that was, etc.Yes, your right.. Both r the good option to have but to have is the first step and the important step to maintain the documentation for errors💚😀.. Thank you for sharing your experience...