Explore >> Select a destination
|
You are here 
|
qsantos.fr | ||
| | | | |
mislav.net
|
|
| | | | | How to settle on whether to merge or rebase at specific points in a team-shared git workflow. | |
| | | | |
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 | |
| | | | |
8yd.no
|
|
| | | | | Git squash takes your commits and squashes them together, usually into one commit. Useful for creating one commit if you've got a lot of smaller commits that creates a messy Git history. Git rebase ... | |
| | | | |
www.morling.dev
|
|
| | | As a software engineer, I like to automate tedious tasks as much as possible. The deployment of this website is no exception: it is built using the Hugo static site generator and hosted on GitHub Pages; so wouldn't it be nice if the rendered website would automatically be published whenever an update is pushed to its source code repository? | ||
