igor_marques
Re:Delivery Reports – Reasons to Adopt This Practice // Leadership Qui...
on Thursday March 02, 2023 @01:06PM (#34999373)
How a simple practice can add a lot of value to a team's work.
Git Basics: Rewriting a branch's commit history from scratch
Remote Work: Introduction and Tips
Simple Ways to Improve the Health Endpoints of Your Apps
Monitoring Your App's Health with Sickbay and the Nurse
Git Basics: Combining two (or more) commits into just one
Git Basics: Adding more changes to your last commit
Good communication in software development teams
Re:Git Workflow Basics
on Wednesday August 17, 2016 @02:19PM (#12306965)
thanks for pointing this. It's fixed!
Re:Git Workflow Basics
on Wednesday August 17, 2016 @10:18AM (#12304867)
The rebase would ideally be the last thing you do on your branch, and very carefully.
And I also mention in the post that we should always use what's best for our teams, so if the squash merge works best for you, go for it! :)
Re:Git Workflow Basics
on Wednesday August 17, 2016 @09:55AM (#12304681)
Nothing stops you to use continuous integration with this workflow. For instance, Travis-CI and Codeship support branching (they can tell you if the new build will be fine or not).
I didn't mention that in the post because it's intended for beginners and adding that info there could maybe be a little too much :/
Git Workflow Basics
Rspec: Writing Custom Matchers (for Newbies)
An easier way to write coding tutorials
Hi, guys,I'm developing this app that makes it really easy to write tutorials with code examples from github:http://that-s-the-way-you-do-it.herokuapp.comYou can just grab a git file URL, paste it in the text editor and your code will be imported right away!(other urls imported now are: lines, line interval, commits and pull requests)The result is something like...