> such as closing JIRA tickets
I'm not a big fan of JIRA myself, but even cool startups need to use an issue tracker?
I'm not a big fan of JIRA myself, but even cool startups need to use an issue tracker?
>> vi main.ex
>> # No tests needed thanks to BEAM ;)
>> git add -A
>> # No need for descriptive commit messages; we spend our time on the important stuff ;)
>> git commit -m 'New commit'
>> # Rockstars push straight to production
>> git push origin master
Am I doing this right?? /s
You have to self-tase one second for every commmit you blew away.
Top score is 4 seconds.
If you have conflicts on a feature branch I guess you aren't the only one working on it and as soon as that's the case force pushing is generally a bad idea unless you coordinate carefully with the test of the team.
The only time I ever force push is on a feature branch that only I work on and I want to amend the commit I just pushed a second ago.
I am not convinced. Instead, you'd need a reward for every cleanly committed line of code.
But elixir does not have main file so it is ok :p