New words for the vocabulary #9
Conversation
|
@edualfaro , this is a nice long list! It's a great starting point for others to build on. One small change, could you move your list to a separate file named |
|
For sure @colevandersWands I will move to another .md file. Before the pull request I was think what will be the best way for adding new vocabulary, in the same file and then later create "some kind of Index", or by different files. Thank you for the explanation. I will close this pull request. |
|
@edualfaro , you don't need to create a new PR. You can always make changes on the same branch and push the changes. the PR will update. The idea of a PR is that it adds one change and gives everyone a single place to discuss those changes before they're merged. Refactoring from the README to a separate file is still part of the same change |
|
Ok @colevandersWands, trying to understand everything... |
gelilaa
requested review from
gelilaa
and removed request for
colevandersWands
| ## Fetch | ||
| By performing a Git fetch, you are downloading and copying that branch’s files to your workstation. Multiple branches can be fetched at once, and you can rename the branches when running the command to suit your needs. | ||
|
|
||
| ## Fork |
There was a problem hiding this comment.
forks are actually a GitHub thing (or GitLab, or any other site). These platforms host git repositories and link them with your user account, but behind the scenes they use git. When you fork a repository it's more like creating a branch connected to a different account. you can also think of it like this: there is no git command to fork a repository from your CLI, but there is a button to do it from GitHub
You could resolve this by either making a separate file github.md and defining "fork" over there, or you could split this file in two with a divider and have words for both Git and GitHub (git-github.md or some such name)
Hope them(words) helps ;-D