/explore
|
You are here 
|
blog.oddbit.com | ||
| | | | |
www.ncameron.org
Crafting a beautiful PR is not a high priority for a lot of people, but I think it should be! In this post, I'll expound on what a good, well-organised PR looks like, why you should do that, and how you can do that. This is an opinionated post, not |
|
| | | | | ||
| | | | |
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... |
|
| | | | | ||
| | | | |
blog.tracefunc.com
Just a random coder writing about technology, web development, and various other geeky topics. |
|
| | | | | ||
| | | | |
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... |
|
| | | |||
