3 ms·
Testing after merging with develop is a very, very bad practise. And there're plenty of tools to help you don't do that, just kick a build to run all your tests
by ktzar 12y ago
Testing after merging with develop is a very, very bad practise. And there're plenty of tools to help you don't do that, just kick a build to run all your tests, which will add a tick or a comment to the branch's PR. And never merge anything without that tick or comment.
- yegor256a 12y agoTotally agree. Testing should be done BEFORE merging, like this article explains: http://www.yegor256.com/2014/07/21/read-only-master-branch.html http://www.yegor256.com/2014/07/21/read-only-master-branch.h...