4/15/2024 0 Comments Github desktop upload to fork![]() 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. Separate screenshots for windows and mac would be helpful, but we can create a followup issue, if they're not done here.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).Update the procedural in the "Forking repositories" section to match the new flow, modeled after previous sections and using reusables for each procedural.Add conceptual information that describes the fact that folks will be asked how they plan to use the fork and the consequences of answering each way (e.g., issues opened in Desktop will be created in the upstream repository).Add an additional sentence to the conceptual information at the beginning of the "Forking repositories" section to explain why a user might want to fork a repository for their own use.In Cloning and forking repositories from GitHub Desktop: Remember to keep conceptual information separate from the procedural. ![]() Note: For the person who picks up this issue. ![]() Let's keep this information focused on very new users. It now asks whether users want to fork a repo to work independently or to contribute to an upstream repo.Īudience: Forking a repo can be a confusing concept to new users looking to participate in open source. This feature provides a new flow to forking a repo. We might need to split it into two separate issues to get screenshots, but maybe that's not required for cloning? This article has a mac and a windows version. Download the current beta version of Desktop to take any screenshots. Use this Desktop issue, Provide a way to more easily work with a maintained fork, to understand the context of this change.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |