Git

Recently my company has switched code repositories, from Gitlab to GitHub. I already have a personal GitHub account so I find myself in a position where I have two GitHub accounts. I authenticate using ssh keys, but GitHub does not authenticate two separate accounts using the same keys. Despite generating a new ssh key for my new corporate account I found myself unable to access my organisations repositories.

Continuous Integration (CI) is not a tool but a practice of continually merging in new behaviour/features into a released product. To facilitate this practice without exposing end users to unstable behaviour and bugs, testing needs to be standardised and automated. It’s no wonder then that CI is often associated with Test Driven Development (TDD), which mandates that you write your tests first, working backwards to the write the minimal code that should pass each test.

I’ve been working with git for quite a while now. I’ve been happily working with git for almost as long. After some in-person training and referring to Happy Git for R, things finally clicked when I found a rhythm to all these strange commands. The git flow I found has helped me not only with what git command I want to use (is it a push? is it a merge?), but also when and in what order to do so.

Gitlab runner in a docker container. Compatible with Raspberry Pi