Explore >> Select a destination
|
You are here 
|
blog.notmyhostna.me | ||
| | | | |
128bit.io
|
|
| | | | | I been trying to use Git more and more to help me learn it. My first step was using it for the pre on this blog but I have also been using it on some small projects I been work on for myself. Git works just fine locally and still is able to use all the features it has but to really take advantage of Git you need to setup a remote repository and here is how to do it. | |
| | | | |
brandont.dev
|
|
| | | | | [AI summary] This post explains how to use Git hooks to create an automated CI/CD pipeline for deploying static websites to a remote VPS. | |
| | | | |
jfr.im
|
|
| | | | | How to create a Git repo you can push to, with a real copy of HEAD in the work tree. | |
| | | | |
wittchen.io
|
|
| | | When you fork GitHub repository, you usually want to have your fork up to date with the original repository. You can update your fork in a few easy steps. Just look at the following example of the Git commands: Add the remote, call it upstream: git remote add upstream https://github.com/whoever/whatever.git Fetch all the branches of that remote into remote-tracking branches, such as upstream/master: git fetch upstream Make sure that you're on your master branch: | ||
