Git

I've used Git since my earliest projects, and I use it for much more than commits and merges: hooks that run checks, automation workflows, contributions to open-source projects, and everyday teamwork.

Git hooks

One of my hooks runs a Bash script I wrote on every commit: it checks the licenses of the packages the project depends on and flags a dependency whose license doesn't fit the moment it enters a commit, before the code is shared. Hooks are exactly how I run checks automatically at the right moment.

GitHub workflows

I write GitHub Actions workflows for builds, tests and deploys: the one that publishes this site's frontend, the matrix builds of the Go services at HSPI, the one that rebuilds my resume every month. They're described on the CI/CD page.

Pull requests to open-source projects

I've opened seven pull requests in five projects, and six were merged: DDEV, CodeIgniter 4 and Shield (told on the CodeIgniter page), gratelets and the Astro docs (on the Astro page). The flow is always the same: fork, branch, pull request, maintainer review.

GitHub, GitLab and GitBucket

I've worked with all three platforms. At TUN2U, in teams of at least ten developers, work went through branches and pull requests handled rigorously. My public projects are on my GitHub profile.