When synchronising, a .log/gin.log file is created or updated.
So there is always a change to push, and stupid commits can be done (no change apart from the fact that it was synchronised).
I see different solutions:
add .log/ to gitignore (but one may want to access it if people have problems)
only write in the log if there is a problem
having one file for logs that is ignored, and one for problems that is not
When synchronising, a .log/gin.log file is created or updated.
So there is always a change to push, and stupid commits can be done (no change apart from the fact that it was synchronised).
I see different solutions:
- add .log/ to gitignore (but one may want to access it if people have problems)
- only write in the log if there is a problem
- having one file for logs that is ignored, and one for problems that is not
having one file for logs that is ignored, and one for problems that is not
I think I like this the most. We could have a transaction log that stores everything and an error log that gets updated (and pushed) when an error occurs.
> having one file for logs that is ignored, and one for problems that is not
I think I like this the most. We could have a transaction log that stores everything and an error log that gets updated (and pushed) when an error occurs.
When synchronising, a .log/gin.log file is created or updated.
So there is always a change to push, and stupid commits can be done (no change apart from the fact that it was synchronised).
I see different solutions:
I think I like this the most. We could have a transaction log that stores everything and an error log that gets updated (and pushed) when an error occurs.