- GITHUB DESKTOP PULL REQUEST HOW TO
- GITHUB DESKTOP PULL REQUEST SOFTWARE
- GITHUB DESKTOP PULL REQUEST CODE
While Git uses a command line interface, GitHub was created to give Git a slicker looking web interface. Because the majority of work that we do at SparkFun is on smaller projects, we use only a fraction of its capabilities.
GITHUB DESKTOP PULL REQUEST SOFTWARE
Git is a software management tool designed for extremely large coding projects (such as Linux).
GITHUB DESKTOP PULL REQUEST CODE
GitHub allows one person to manage their own projects (also called revision or version control) and it also allows lots of people to work together on large projects (source code management). This is a bit tedious, and when a project gets longer than a few lines of code, email is not a viable way to collaborate on projects. If the code was just a file on someone’s website you’d have to send them an email and suggest the improvements. There’s a couple improvements that could be made to this code ( analogRead returns an int not a byte!).
GITHUB DESKTOP PULL REQUEST HOW TO
The most common use for repos are for managing large code projects but repo tracking is good for a variety of applications in the hardware world including PCB layouts, firmware, datasheets and documentation.įor example, let us imagine someone has created an Arduino sketch to demonstrate how to read an analog sensor.
If there’s ever a problem with a file you can go back in time to figure out what changes you made. Think of a repo as a folder of files and all the changes made to the files are recorded. If B was forked at commit C and d e f were made on B/master, we would get the same picture after the pull request from B/master to A/master as we did from A/document_more_things.Using GitHub a tutorial Whether document_more_things is in A or B actually doesn't matter very much, because Git only cares about commits and their ancestries. When the pull request is accepted, history will look like this, with a g merge commit: a - b - c - g # master For example, if someone created an A/document_more_things branch and made some commits (and syncs, which in Git parlance would be a push from their local repository A to GitHub's remote repository A), the repository might look like this: a - b - c # masterīoth the master and document_more_things branches exist in repository A, without the need of a forked repository B, and the author can open a pull request from A/document_more_things to A/master. Knowing that, in fact you can open pull requests between any branches that have a common commit history. When you see the pull request opened from repository B to repository A, really it's being opened from branch B/master to branch A/master. That is, repositories A and B each have a master branch. In your case, it sounds like there are two interesting branches so far: A repository may contain many branches, and when you create a pull request, you pick which branch you want to merge into which other branch. Pull Request behavior will be clearer if you start thinking in terms of branches instead of repositories. I can't try it out because that button is always greyed out for me (maybe because I own the repository?)Īnd can a user make a pull request directly into repository A from GitHub Desktop - or will it always be a two-step process via repository B?
If it's repository B, then what's the difference between commit/sync and the pull request button? I get that.īut GitHub Desktop also has a 'Pull Request' button, and I don't get who it's making the request to! Is it repository A or repository B? Or something completely different? If they want to then copy the edits to repository A, they go into GitHub and make a pull request. In GitHub Desktop they can use 'Commit to Master' and then hit the 'Sync' button. They make edits locally and then open GitHub Desktop. They can then click 'Clone in Desktop' to get a local copy. If someone wants to make updates they fork that repository to one of their own (call it 'B'). Here's the scenario: I have a GitHub repository (call it 'A'). I can't find an answer in the GitHub help (I did look) and I did ask some software developers (I'm using GitHub to store documentation) and they didn't know either! Apologies if this is too basic, or a duplicate, but I'm confused here.
0 kommentar(er)
