paint-brush
Don’t use GitHub’s “Rebase and Merge” workflow (yet)by@jcfrancisco
981 reads
981 reads

Don’t use GitHub’s “Rebase and Merge” workflow (yet)

by Carlo Francisco2mMarch 6th, 2017
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

In September last year, <a href="https://hackernoon.com/tagged/github" target="_blank">GitHub</a> <a href="https://github.com/blog/2243-rebase-and-merge-pull-requests" target="_blank">introduced</a> a couple of new behaviors to its “<a href="https://hackernoon.com/tagged/merge" target="_blank">Merge</a>” button as alternatives to the standard of creating a new merge commit every time. Namely, “Squash and Merge” and “Rebase and Merge.”

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - Don’t use GitHub’s “Rebase and Merge” workflow (yet)
Carlo Francisco HackerNoon profile picture
Carlo Francisco

Carlo Francisco

@jcfrancisco

L O A D I N G
. . . comments & more!

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite