One remark:
what contains your master branch is actually a part of your release management process and many times it will not be a production code. See for example Kubernetes project - production releases are in branches and master branch is used for ongoing development.
Which of course doesn't mean that the code should not be tested.
Very good article.
One remark:
what contains your master branch is actually a part of your release management process and many times it will not be a production code. See for example Kubernetes project - production releases are in branches and master branch is used for ongoing development.
Which of course doesn't mean that the code should not be tested.
Sure! It depends on the infrastructure you use every time!