Skip to content

Blog Post Proposal: "How to Keep Your Git History Clean with Interactive Rebase"

Proposal

Suggested Title: "How to Keep Your Git History Clean with Interactive Rebase"

Interactive Rebase is sometimes called the "Swiss Army Knife" of Git - because it contains so many different tools, for so many different use cases! However, there's one main, overarching use case: ​cleaning up your local commit history.

I'd like to help developers better understand...

  • what benefits they gain from using Interactive Rebase
  • some potential use cases
  • how exactly they can use it

About the Author

I have 10 years experience of writing about Git - and I've already written for the GitLab blog before: https://about.gitlab.com/blog/2017/01/30/getting-started-with-git-lfs-tutorial/

Checklist

  • If you have a specific publish date in mind (please allow 3 weeks' lead time)
    • Include it in the issue title and apply the appropriate milestone (e.g. Blogs October 2020)
    • Give the issue a due date of a minimum of 2 working days prior
    • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
  • If time sensitive
    • Add ~"Blog: Priority" label and supplied rationale in description
    • Mention @rebecca to give her a heads up ASAP
  • If wide-spread customer impacting or sensitive, mention @nwoods to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue
  • If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS, apply the Partner Marketing label, and see the blog handbook for more on third-party posts
  • If the post is about one of GitLab's customers, mention @KimLock and @FionaOKeeffe, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts
  • Indicate if supporting an event or campaign
  • Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)
Edited by Rebecca Dodd