5
Yes, and no.
Is the action you are putting into the script worth it?
At work we have issues with git on windows environments. The file system is case-insensitive and leads to all sorts of fun. We using the pre-commit hook to ensure that all branch names are lower case. This is a quick check that saves a lot of hassle.
Our post commit hook checks to see if ...
4
There are two techniques that work together to avoid this type of scenario from occurring:
Step 1: write a failing test before fixing the bug
When the bug has been found, the first thing to do is to write a test that will pass when the bug is fixed and thus it fails whilst the bug still exists. The dev then fixes the bug and in the process makes the test ...
3
all the users who still have 1.2 installed on their phone are still able to use the app without problem?
Not being an expert of mobile dev, but it seem to me forcing updates is the regular workflow for phone apps in these cases, if such breaking change would happen the v1.2 should have a mechanism to refuse launching until it is updated. This is at least ...
2
I wholeheartedly second David Arno's suggestions about failing tests and code reviews. Also, there are often ways to write the code to make it less susceptible to that kind of error in the future.
For example, if the error was created by calling a function before its prerequisites were met, you can split your classes differently so that would create a ...
2
What's the matter ?
I understand that this is extremely annoying. But this can happen when the rules of the game are not clearly explained.
Depending on contractual matters, the customer may or may not be allowed to intervene on the code. Even if the customer may not interfere, your boss may accept it for commercial reasons (e.g. your company is very ...
1
This depends a lot on your teams branch/merge and working model, on the quality of the linter rules, the quality of the unit tests and the actual running time of both.
When developers mainly commit to their local branch, or commit or push to an isolated feature branch, the influences of a non-clean commit on other team members are quite low, so they are ...
Only top voted, non community-wiki answers of a minimum length are eligible
