🔥Let’s Do DevOps: Get All GitHub Repo Branches (Even if there’s Thousands)

This blog series focuses on presenting complex DevOps projects as simple and approachable via plain language and lots of pictures. You can do it!

Hey all!

I’ve been writing an ongoing project I’m calling our GitHubCop — it’s a tool that iterates over every repo we have (and we have thousands) and sets all the settings, branch policies, permissions, etc. on each of them every day.

I’ve been primarily relying on GitHub’s REST API + a lot of clever bash tricks. It isn’t the most modern language, but it makes sense to me, and heck, it works. As I’ve been developing the project I’ve found a few rough edges, and I wanted to write about one of them I stumbled on recently — grabbing a list of ALL the branches in a repo.

After all, we only want to set branch policies for branches that exist, right? So let’s talk about why this seemingly simple question isn’t simple, and how to solve it.

I’ve Moved To Lets Do DevOps

From here on out, all content will be published on Lets Do DevOps for free. I want to give back to the community as much as I’m able. Please subscribe there to avoid missing any content. Thanks all ❤.

You can find this article here:

🔥Let's Do DevOps: Get All GitHub Repo Branches (Even if there's Thousands)