Git has transformed how version control has been and Metal Toad has written extensively on how to leverage this powerful tool. The following list include CI/CD, porting to Git and GitHub specific hacks. Be sure to check out our top 5 Git tips and tricks.
-
How to Integrate GitHub PRs with Bamboo CI
Bamboo / GitHub integration isn't perfect – perhaps because Atlassian wants to steer you towards Bitbucket (their GitHub competitor). Out of the box, there are several headaches. Below, I'll cover these, and how to solve each one
-
Git: Push All Branches to a New Remote
Here's a scenario some of you might have encountered with your Git repositories. You have a working copy of a Git repo, say from an old server. But you only have the working copy, and the origin is not accessible. So you can't just fork it...
-
Secrets to Project Happiness Using Git
I have worked with dozens of projects over my career, on platforms ranging from Drupal to Yii to Django to AngularJS to ASP.NET.
-
Git: Always Be Branching (ABB)
In this week's episode, we'll be revisiting the Git workflow in greater detail. I was originally going to discuss Capistrano too but quickly realized that would make for a really long blog post so I will save Capistrano for next week. However, I will say that they both have a similar role in helping you organize your data.
-
Git: Always Be Committing (ABC)
For a junior in the working world, that word takes on a whole new meaning if you are looking at it from the perspective of professional growth. Being a junior in any field can consist of some pretty broad results depending on a number of factors...
-
Receiving Git Attribution for Your Drupal.org Patches
If you contribute patches to the Drupal issue queues, you often spend a lot of time and hard work getting that patch through the review process. Even though we do it for the good of the community, once it is all said and done, it's nice to get a little acknowledgement.
-
A beginner's guide to GIT BISECT - The process of elimination
The slowest, most tedious way of finding a bad git commit is something we've all done before. You checkout some old commit, make sure the broken code isn't there, then checkout a slightly newer commit, check again, and repeat over and over until you find the flawed commit. Using git bisect is a much better way. It's like a little wizard that walks you through recent commits, asks you if they are good or bad, and narrows down the broken commit. In this blog post, I encourage you to create a fresh git repository and walk through each step. Hopefully, you'll gain an intrinsic understanding of git bisect by the end of the exercise.
-
Mechanizing Git bisect: Bug hunting for the lazy
Like this article? Check out our top 5 Git tips and tricks Git bisect is a powerful automated tool for searching deep into a project's history. Instead of searching for relevant commit messages (git log) or patches (git log -S), bisect actually allows you to run a functional test on each revision until the first bad commit is identified. (Okay, it doesn't test every revision, it performs a binary search, which results in at most log2(N) tests. This allows a relatively large history to be searched quickly.) The test can be done interactively, with the human performing each check, or mechanically if you can supply a testing script. Randy Fay has done a nice screencast on the interactive method; this post will instead focus on mechanizing the process. For an example, let's look at a core Drupal bug that impacts this very site: #812990: Search page title changes to Home. For the moment, we'll pretend the cause of this bug isn't already known, and hunt it with git-bisect.
-
A Git + Drupal Primer
Now that the Drupal community's migration to Git is in full swing, it's a great time to switch your own projects as well. Curious? Perhaps you saw the Git panel in San Francisco, or maybe you've listened to Sam Boyer campaigning passionately at your local DrupalCamp. Is there a rebel in your office who keeps going on about how much better life can be with git-svn? (How ironic that Subversion is now the establishment.) If you're just getting started, here are some tips I've collected over the last year. Or if you're already a Git ninja, here's how you can help.
-
Using git-svn to manage standard and non-standard branches
When Webchick announced that Drupal was moving to Git at Drupalcon, our office erupted in pleasure at the news. Lots of great Drupalists are already using Git and there's even an unofficial ...
-
An unexpected occurence with Git, how it made our life easier this time
In my experiences in the past working with external contractors is often a pain, especially the final merge where you try to incorporate all their code. I've always been a huge proponent of Subversion for SCM but today I saw an example where Git knocked the socks off of Subversion.