4 ms·
Yeah, pushing untested code to master is not such a great way to work. Push to a remote branch other than master, test it there, then merge it into master. Tha
by SteveNuts 10y ago
Yeah, pushing untested code to master is not such a great way to work. Push to a remote branch other than master, test it there, then merge it into master.
That's pretty much git 101
- njharman 10y agoThat's pretty much software development 101. Been happening for decades before git.
- pc86 10y agoOr test locally? I work in government contracting so everything is .Net and TFS, but even in this environment it's trivial to make sure your code isn't objectively broken: 1. Click "Run all tests" On your local machine even thousands of tests only takes a few seconds including the build process. We've got automated testing in the dev and test environments as well but if you're failing those there's a failure in workflow somewhere. There's very little reason to fail a test or to have a broken build in source control.