Just Write Click

Technical writing with Continuous Integration and docs-as-code

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code
You are here: Home / techpubs / GitHub Pro account or GitHub Free account for Technical Writing

January 14, 2019 by annegentle

GitHub Pro account or GitHub Free account for Technical Writing

GitHub Pro account or GitHub Free account for Technical Writing

Should I downgrade or upgrade my GitHub account, now that the free tier has unlimited private repositories? I could save seven dollars a month, 84 dollars a year.

I looked into this question for myself, and didn’t get enough info from the pricing page at github.com/pricing when the change was first announced. So, I logged a help ticket with GitHub, and as I’ve experienced before when I was working on the Docs Like Code book, they were very responsive! I had an answer by the next morning in my inbox.
 
My specific question was, “What are ‘advanced code review tools,'” quoting from the pricing page. I must note: the great thing about asking this question is that I see that the pricing page now points to the answer to the question! The link is now available, and the text has changed to “Advanced tools and insights.” My inner product manager heart jumped with glee.

What do you get with the GitHub Pro Account?

What I learned is that the added features are related to many things that are useful for doc publishing and reviews, using private repositories on GitHub. These features and tools on your private repos include these, with links to help pages where available:

  • Unlimited collaborators (with Free you get three collaborators per repo)
  • GitHub Pages
  • Wikis
  • Protected branches
  • Code owners
  • Repository insight graphs: Pulse, Contributors, Traffic, Commits, Code frequency, Network, and Forks

Now, you can do all those things on public repositories with your GitHub Free account. So what does this mean for people using GitHub for tech writing? I think it’s similar to any use case for development. If you want to work in private with more than three collaborators, and publish from a private repo to a public webpage using GitHub Pages, you want a GitHub Pro account. If you’re pretty sure you’re always going to work in public repos in the open, then you don’t lose anything by staying with a Free account.

For me, I’ll keep paying my $7 a month as I’ve found it super valuable to work through things either on my own or in small groups. I also like protected branches, sometimes for my own safety. And maybe, or at least I’d like to think so, I’m supporting students and starting users of GitHub by supporting GitHub itself.

Related

Filed Under: techpubs, tools, work, writing Tagged With: docslikecode, git, githubpages

More reading

Bubble graph showing sources of developer support data

I’ve been thinking a lot about developer support at Cisco recently, especially for the way the world works today with multiple cloud providers. This post is a re-publish of my talk from over five years ago, but the techniques and tools for listening and helping others are still true today. At Rackspace, we watched several […]

Cisco DevNet is our developer program for outreach, education, and tools for developers at Cisco. From the beginning, the team has had a vision for how to run a developer program. Customers are first, and the team implements what Cisco customers need for automation, configuration, and deployment of our various offerings. Plus, the DevNet team […]

I had a great talk with Ellis Pratt of Cherryleaf Technical Writing consulting last week. Here are the show notes, full of links to all the topics we covered. Podcasts are great fun to listen to and participate in, if a bit nerve-wracking to think on your feet and make sure you answer questions succinctly […]

At the beginning of this year, I worked hard to summarize my thoughts on API documentation, continuous publishing, and technical accuracy for developer documentation. The result is an article on InfoQ.com, edited by Deepak Nadig, who also was forward-thinking in having me speak to a few teams at Intuit about API documentation coupled with code. Always […]

Recently on Just Write Click

  • A Flight of Static Site Generators: Sampling the Best for Documentation
  • Try a GPT about “Docs Like Code” to ask questions
  • Discipline and Diplomacy: Docs in the Open
  • Let’s Find Out: When Do Static Site Generators Do Rendering?
  • GitHub for Managing Tech Docs

Just Write Click in your Inbox

Enter your email address to subscribe to Just Write Click and receive notifications of new posts by email.

Read More

  • Privacy Policy
  • About Anne Gentle, developer experience expert
  • Books by Anne Gentle
    • Conversation and Community
    • Docs Like Code, a Book for Developers and Tech Writers
  • Woman in Tech Speaker Profile
  • Contact

Books

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code

Copyright © 2025 · WordPress · Log in