/explore
|
You are here 
|
blog.bloomca.me | ||
| | | | |
www.integralist.co.uk
Introduction Rebase before merge Example (Bonus) Modifying content within an interactive rebase Introduction This is a quick post to cover a GitHub workflow that is utilised by our specific team (Frameworks) here at BBC News. The basis of our workflow is this: Open a GitHub PR (Pull Request) by creating a new feature branch from master Make feature specific changes and request a code review If given a "thumbs up", this means the PR author is allowed to handle merging the PR The merge process requires a s... |
|
| | | | | ||
| | | | |
andreabergia.com
Git has an excellent tool designed to help you reorder the commit history: interactive rebase. This can be excellent if you want to keep the history clean, so that it helps other programmers understand the logic behind the changes rather than the actual sequence of commits. Let's walk through an example. Let's write some history Link to heading Let's start by creating an empty project in a new directory: |
|
| | | | | ||
| | | | |
petelevasseur.com
Pete LeVasseur's Blog - Engineering, Rust, Automotive, and more |
|
| | | | | ||
| | | | |
blog.kdgregory.com
I like to provide a nice, clean history in my pull requests. Reviewers should be able to follow each commit, and see how the functional... |
|
| | | |||
