![]() No more -set-upstream origin or need to setup complicated aliases. Starting from Git 2.37.0, you can run just git push to push new branches. Skip -set-upstream origin when pushing new branch to Github Other configs and setup that can be nice: This will be used later in the "update your Fork" section. ![]() This will set up Roll20's repository as an remote called upstream for your local copy, where you can pull updates from. Navigate your CLI to be inside the folder created in Step 6.When you later use commands like git push or git fetch, it will act as if you had typed git push origin or git fetch origin, interacting with your GitHub fork. This will automatically set your GitHub fork as the default remote (called "origin"). Now git is downloading and making you a local copy of your GitHub repository, and it may take some time. (for github user Anduh this would look like: git clone ). Type git clone and the url you have from Step 5.Copy it somewhere easily accessible for Step 6. On the left side is a green "Clone or Download" button, and if pressed, show an url that ends in ".git", which you will need in the next step. Open up your browser and navigate to your Github Fork. Open up a command line prompt/interface(CLI) in this folder.Go to your file manager, and navigate to a folder where you want to place your copy of the roll20 repo.Download and install Git on your computer.Now you have your own fork of the repo, that you can do whatever you want with, but it's still only on the internet, and we want to make a local copy on your computer. It will ask you to name your fork, and my recommendation is to keep the default name, as it will keeps things simple later). (When logged into GitHub, press the "fork" icon in the upper left corner of this page. Have your own GitHub account, and have a fork created from Roll20's repository.After completing Step 6, see the Sparse Checkout section for a series of alternate setup instructions to only clone the files you need. The steps below outline how to clone the entire repository onto your computer. will be needed for the "Update your Fork"-section if you otherwise already have a github fork and a local copy. If you've already worked with a GitHub desktop or other graphical user interface, some steps are redundant, and should be skipped if it seems to create duplicates. In some places help for Windows-users are linked, while Linux-users are assumed to knowing or figure out the basics. This guide is made with Linux in mind, but should work universally, if you install & setup Git on your computer with the unix-compatible option.The GitHub repository for Character Sheets are used as an example here, but it works the same with any other GitHub project you have forked, such as Roll20's API Script repo. ![]() The author of the guide has English as a second language. If you encounter words you don't understand, google for it together with "Git" or "Github", as it is likely a term linked to them. Start with reading the guide's Glossary to understand commonly used words or phrases in the guide.This is to make revisiting the guide quicker when you already remember what each step means, but don't remember the exact commands/actions or their order. In most places/steps, it's first written in bold the action to be done, and afterwards an explanation of what it does, and why it's done.GitHub is essentially a website hosting Git, with a few extra features. Learning to use Git gives you a better understanding of how Git and GitHub works.Using the CLI makes it easier to troubleshoot, as you clearly know what steps you took, and can see the messages or error message the CLI gives back, which you can then search for on the web or share with others.Git command line(CLI) have more guides & documentation than the GitHub Desktop/Browser.6.8.3 Updating your branch when your collaborator have updated theirs.6.8.2 Creating a sheet update suggestion & sending it to your collaborator.6.8.1 Create a copy of someone's branch.6.3 Submit a Pull Request to Roll20(on Github).6.2 Creating a small fix and saving your progress.6.1.1 Updating a work-in-progress branch.4.2 Removing Directories from Sparse Checkout.4.1 Adding Directories to Sparse Checkout.1 Why Git CLI instead of GitHub Desktop?.It's recommended by those who do lots of work on character sheets and/or juggles more that one sheet at a time. The guide is aimed towards people who want to work with Roll20's Character Sheets and be able to interact with Roll20's Github & Git through the command line(CLI).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |