It all comes down to one thing

Never commit directly onto the master branch. Instead, commit to a designated “unstable” branch until the code has been tested.

The way to do this is to just do your work on your own local branch. To add to this, branch off for each feature/bug fix you are working on. For me, this would look like:

  • git checkout dales_branch (assuming it already exists)
  • git checkout -b myfeature
  • [ code code code ]
  • git add . && git commit -a -m “coded my feature but it’s not tested yet”
  • git checkout unstable
  • git pull –rebase origin unstable
  • git push origin unstable
  • [ test test test ]
  • git checkout master && git pull –rebase
  • git rebase origin unstable

If everyone in your group follows this workflow, everything will be kept nice and organized.

bpftrace contributions

# bpftrace internalsI've written up some of what I've contributed to bpftrace, which I think cangive a nice overview of bpftrace internal...… Continue reading

Production Breakpoints

Published on July 21, 2019

usdt tracing report

Published on April 19, 2019