diff --git a/README.md b/README.md
index d33c584c25f..e7cf0fbf9aa 100644
--- a/README.md
+++ b/README.md
@@ -180,5 +180,5 @@ Now let's get you started with contributing to other projects. We've compiled a
|
|
|
|
|
|
|
| ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [GitHub Desktop](github-desktop-tutorial.md) | [Visual Studio 2017](github-windows-vs2017-tutorial.md) | [GitKraken](gitkraken-tutorial.md) | [Visual Studio Code](github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](sourcetree-macos-tutorial.md) | [IntelliJ IDEA](github-windows-intellij-tutorial.md) |
+| [GitHub Desktop](gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](gui-tool-tutorials/github-windows-intellij-tutorial.md) |
diff --git a/github-desktop-old-version-tutorial.md b/gui-tool-tutorials/github-desktop-old-version-tutorial.md
similarity index 55%
rename from github-desktop-old-version-tutorial.md
rename to gui-tool-tutorials/github-desktop-old-version-tutorial.md
index faa0aa28a6e..ee22ab528b2 100644
--- a/github-desktop-old-version-tutorial.md
+++ b/gui-tool-tutorials/github-desktop-old-version-tutorial.md
@@ -1,5 +1,5 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
@@ -13,7 +13,7 @@ It's hard. It's always hard the first time you do something. Especially when you
Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are, the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun.
-
+
If you don't have GitHub Desktop on your machine, [install it](https://desktop.github.com/).
@@ -28,15 +28,15 @@ Now clone this repo to your machine.
Open the GitHub Desktop app and click on the `+` on the top left.
-
+
If it is not already selected, click on `Clone`. Then choose first-contributions and then click on `Clone first-contributions`
-
+
Choose the directory on your machine you would like to clone first-contributions into
-
+
Now you have copied the contents of the first-contributions repository in github to your computer.
@@ -44,13 +44,13 @@ Now you have copied the contents of the first-contributions repository in github
Now create a branch by clicking on the branch icon at the top left:
-
+
Name your branch add-your-name. For example, add-crawleya
Click on `Create new branch`
-
+
## Make necessary changes and commit those changes
@@ -58,7 +58,7 @@ Now open `Contributors.md` file in a text editor and add your name to it, then s
You can see that there are changes to Contributors.md and they have been added.
-
+
Now commit those changes:
@@ -68,27 +68,27 @@ Replace `` with your name
Click on the button that says `Commit to add-your-name`
-
+
At the bottom, you can see that the commit has been created.
-
+
## Push changes to github
Click the `Publish` button on the top right.
-
+
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -96,26 +96,13 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share).
You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-### [Additional material](additional-material/git_workflow_senarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_senarios/additional-material.md)
## Tutorials Using Other Tools
-
-|
|
|
|
|
-|---|---|---|---|
-|[Command Line](README.md)|[Visual Studio 2017](github-windows-vs2017-tutorial.md)|[GitKraken](gitkraken-tutorial.md)|[IntelliJ IDEA](github-windows-intellij-tutorial.md)|
-
-## Self-Promotion
-
-If you liked this project, star it on [GitHub](https://github.com/Roshanjossey/first-contributions).
-If you're feeling especially charitable, follow [Roshan](https://roshanjossey.github.io/) on
-[Twitter](https://twitter.com/sudo__bangbang) and
-[GitHub](https://github.com/roshanjossey).
-
-
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/github-desktop-tutorial.md b/gui-tool-tutorials/github-desktop-tutorial.md
similarity index 54%
rename from github-desktop-tutorial.md
rename to gui-tool-tutorials/github-desktop-tutorial.md
index df10e189355..87f59c61dab 100644
--- a/github-desktop-tutorial.md
+++ b/gui-tool-tutorials/github-desktop-tutorial.md
@@ -1,5 +1,5 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
@@ -17,7 +17,7 @@ If you don't have GitHub Desktop on your machine, [install it](https://desktop.g
If you're using a version of GitHub desktop before 1.0, [refer this tutorial](github-desktop-old-version-tutorial.md).
-
+
## Fork this repository
@@ -32,15 +32,15 @@ IMPORTANT: DO NOT CLONE THE ORIGINAL REPO. Go to your fork and clone it.
To clone the repo, click on "Clone or Download" and then click on "Open in Desktop".
-
+
A pop up window will open. Click on "Open GitHubDesktop.exe".
-
+
After you click on "Open GitHubDesktop.exe" the contents will be downloaded to your computer.
-
+
Now you have copied the contents of the first-contributions repository in github to your computer.
@@ -48,11 +48,11 @@ Now you have copied the contents of the first-contributions repository in github
Now create a branch by clicking on the "Current branch" icon at the top and then click on "New branch":
-
+
Name your branch . For example, "add-james-smith"
-
+
Click on `Create branch`
@@ -66,7 +66,7 @@ Example: If your name is James Smith, It should look like this.
You can see that there are changes to Contributors.md and they have been added to the Github Desktop.
-
+
Now commit those changes:
@@ -76,31 +76,31 @@ Replace `` with your name.
Click on the button that says `Commit to add-your-name`.
-
+
At the bottom, you can see that the commit has been created.
-
+
## Push changes to github
Click on File->Options and sign-in to Github.com. Type in your Github username and password.
-
+
Click the `Publish` button on the top right.
-
+
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -108,26 +108,12 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share).
You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-
-### [Additional material](additional-material/git_workflow_senarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_senarios/additional-material.md)
## Tutorials Using Other Tools
-
-|
|
|
|
|
|
|
-|---|---|---|---|---|---|
-|[Command Line](README.md)|[Visual Studio 2017](github-windows-vs2017-tutorial.md)|[GitKraken](gitkraken-tutorial.md)|[Visual Studio Code](github-windows-vs-code-tutorial.md)|[Atlassian Sourcetree](sourcetree-macos-tutorial.md)|[IntelliJ IDEA](github-windows-intellij-tutorial.md)|
-
-## Self-Promotion
-
-If you liked this project, star it on [GitHub](https://github.com/Roshanjossey/first-contributions).
-If you're feeling especially charitable, follow [Roshan](https://roshanjossey.github.io/) on
-[Twitter](https://twitter.com/sudo__bangbang) and
-[GitHub](https://github.com/roshanjossey).
-
-
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/github-windows-intellij-tutorial.md b/gui-tool-tutorials/github-windows-intellij-tutorial.md
similarity index 83%
rename from github-windows-intellij-tutorial.md
rename to gui-tool-tutorials/github-windows-intellij-tutorial.md
index c56992cd98e..e0acbf829d5 100644
--- a/github-windows-intellij-tutorial.md
+++ b/gui-tool-tutorials/github-windows-intellij-tutorial.md
@@ -1,5 +1,5 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
@@ -19,7 +19,7 @@ If you don't have IntelliJ IDEA on your machine, [install it](https://www.jetbra
## Fork this repository
-
+
Fork this repo by clicking on the fork button on the top right of this page. This will create a copy of this repository in your GitHub account.
@@ -29,7 +29,7 @@ Most top-level GitHub Repos (i.e. ones not forked from any other repo) have a sm
## Clone your repository
-
+
The next step is to clone your repo down to your machine so you can begin making changes. IntelliJ IDEA needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon.
@@ -89,11 +89,11 @@ At this point you have completed your change but it still only resides in your r
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -101,22 +101,12 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share).
You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-### [Additional material](additional-material/git_workflow_scenarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
-[Back to main page](README.md)
-
-## Self-Promotion
-
-If you liked this project, star it on [GitHub](https://github.com/Roshanjossey/first-contributions).
-If you're feeling especially charitable, follow [Roshan](https://roshanjossey.github.io/) on
-[Twitter](https://twitter.com/sudo__bangbang) and
-[GitHub](https://github.com/roshanjossey).
-
-
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/github-windows-vs-code-tutorial.md b/gui-tool-tutorials/github-windows-vs-code-tutorial.md
similarity index 66%
rename from github-windows-vs-code-tutorial.md
rename to gui-tool-tutorials/github-windows-vs-code-tutorial.md
index e00dfb7bca1..88d43ecb8f0 100644
--- a/github-windows-vs-code-tutorial.md
+++ b/gui-tool-tutorials/github-windows-vs-code-tutorial.md
@@ -1,5 +1,5 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
@@ -19,7 +19,7 @@ If you don't have Visual Studio Code on your machine, [install it](https://code.
## Fork this repository
-
+
Fork this repo by clicking on the fork button on the top right of this page. This will create of copy of this repository in your GitHub account.
@@ -29,7 +29,7 @@ Most top-level GitHub repos (i.e. ones not forked from any other repo) have a sm
## Clone your repository
-
+
The next step is to clone your repo down to your machine so you can begin making changes. VS Code needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon.
@@ -37,22 +37,22 @@ The next step is to clone your repo down to your machine so you can begin making
Now open up Visual Studio Code. The welcome page of VS Code will pop up. From there press `F1` to open up the bar shown below. Notice that there is already a `>` (greater than) sign in the text field. You can also get to the input prompt by pressing `CTRL-P` and then type the `>` character.
-
+
You may notice that there are already some obscure commands listed below. Those are my recently used commands. So just don't care about them.
-
+
Now type in `git clone`, only `git` or `clone` (it works like a search).
Select the Entry `Git: Clone` and press `Enter`
-
+
Paste the URL of your repository and press `Enter`. This will open up a File Explorer where you can then choose where the Git repository should be stored.
**Important**: Make sure it is the forked repository and not the original one, otherwise it won't work.
-
+
You should see a status popup on the bottom right of Visual Studio Code. After it has finished, you can open up the cloned repository (now a folder on your machine) using the buttons in the dialog.
@@ -60,7 +60,7 @@ You should see a status popup on the bottom right of Visual Studio Code. After i
Open up the command palette again by pressing `F1`. Type in `branch` and select the `create branch` command from there. In the next step type in the name of your new branch, for example `add-david-kroell`. Press enter and the branch will be created. The branch is also already checked out. [What does checkout mean?](https://www.git-scm.com/docs/git-checkout)
-
+
## Make necessary changes
@@ -68,26 +68,26 @@ Open `Contributors.md` and add your name anywhere in the file. This file contain
Copy one of the other contributors' lines and modify it with your name to make sure you get the syntax right - it can be picky.
-
+
## Commit & Push changes to GitHub
On the left side of VS Code is a menu with 5 icons displayed. Select the version control/Source Control icon.
(Shortcut : Ctrl + Shift + G)
-
+
The file explorer displays all files which were changed after the last commit. By hovering the files and clicking the `+` (plus) the files are staged.
-
+
Type something in the line on top of the explorer and press the checkmark. The changes are now committed to your local copy. Now the changes have to be pushed back to GitHub.
-
+
Use the three-dot icon to open up the menu where you select the `Publish Branch` option. This should open up a dialog to put your GitHub credentials in.
-
+
## Submit your changes for review
@@ -95,11 +95,11 @@ At this point you have completed your change but it still only resides in your r
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -107,26 +107,12 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share).
You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-### [Additional material](additional-material/git_workflow_scenarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
-
-|
|
|
|
|
|
|
-|---|---|---|---|---|---|
-|[Command Line](README.md)|[GitHub Desktop](github-desktop-tutorial.md)|[Visual Studio 2017](github-windows-vs2017-tutorial.md)|[GitKraken](gitkraken-tutorial.md)|[Atlassian Sourcetree](sourcetree-macos-tutorial.md)|[IntelliJ IDEA](github-windows-intellij-tutorial.md)|
-
-
-## Self-Promotion
-
-If you liked this project, star it on [GitHub](https://github.com/Roshanjossey/first-contributions).
-If you're feeling especially charitable, follow [Roshan](https://roshanjossey.github.io/) on
-[Twitter](https://twitter.com/sudo__bangbang) and
-[GitHub](https://github.com/roshanjossey).
-
-
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/github-windows-vs2017-tutorial.md b/gui-tool-tutorials/github-windows-vs2017-tutorial.md
similarity index 67%
rename from github-windows-vs2017-tutorial.md
rename to gui-tool-tutorials/github-windows-vs2017-tutorial.md
index 8edb5fb48f5..640d623a51a 100644
--- a/github-windows-vs2017-tutorial.md
+++ b/gui-tool-tutorials/github-windows-vs2017-tutorial.md
@@ -1,5 +1,5 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
@@ -16,7 +16,7 @@ If you don't have Visual Studio 2017 on your machine, [install it](https://www.v
## Fork this repository
-
+
Fork this repository by clicking on the fork button on the top of this page. This will create of copy of this repository in your GitHub account.
@@ -26,7 +26,7 @@ Most top-level GitHub repos (i.e. ones not forked from any other repo) have a sm
## Clone your repository
-
+
The next step is to clone your repo down to your machine so you can begin making changes. Visual Studio needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon.
@@ -34,7 +34,7 @@ The next step is to clone your repo down to your machine so you can begin making
It is now time to jump in to Visual Studio 2017! You will be working in the Team Explorer tab for most of this tutorial. If it is not open by default, click `View > Team Explorer` to open it.
-
+
Team Explorer has many views and there are navigation buttons located at the top to help you find the different areas. To clone a repo, you need to be on the Connect view, which should be the default. If you do not see the 'clone' button, click the green plug at the top.
@@ -42,31 +42,31 @@ Click the `Clone` option under **Local Git Repositories** and paste the URL to y
Click the `Clone` button to initiate the process.
-
+
When the process is complete you will be moved over to the Solution Explorer tab where you can see the contents of your repo. Yours will look different than the screenshot below because things change!
-
+
## Create a branch
Click back to the Team Explorer tab and use the main navigation dropdown to open the Branches view.
-
+
You should see the **first-contributions** repo and the default branch, which is called `master`. Right-click on `master` and choose `New Local Branch From...`.
-
+
Give your branch a name like `add-`, for example: `add-alonzo-church`.
Leave the `Checkout branch` box checked and click the `Create Branch` button.
-
+
You should see your new branch in the list.
-
+
## Make necessary changes
@@ -74,24 +74,24 @@ Open `Contributors.md` and add your name to the end of the list. This file conta
Copy one of the other contributors' lines and modify it with your name to make sure you get the syntax right - it can be picky.
-
+
## Commit & Push changes to GitHub
Switch back to Team Explorer and navigate to the Changes view.
-
+
Enter the information you want to post with your commit and click `Save`. Visual Studio will remember it for future commits.
-
+
**NOTE:** Visual Studio uses a hidden folder called `.vs` to store your personal settings and preferences. The contents of this folder **should not be saved in Git**.
If it has not been ignored already, you may need to tell Git to ignore this folder so it does not send it up to the repo.
This folder has already been ignored in this repo, so you should not have to perform this step...it is just here for your reference for future projects.
-
+
Now you should see a list of changed files and a textbox to type a commit comment. Comments should be in brief but thorough. There is nothing worse than reading through commit comments and seeing this: `"I updated some stuff"`. Take a few seconds to outline your commit. Your team will thank you later, and you might even thank yourself!
@@ -99,17 +99,17 @@ Click `Commit All and Push` to perform a local commit and push your changes back
**NOTE:** Commit can be performed separately from Push. We do both here for convenience. Commit logs your changes locally but they will not be reflected in your GitHub repo until you Push.
-
+
The first time you Push to GitHub, Visual Studio will ask for your GitHub credentials. They will be cached so you should not see this very often.
-
+
After the Push operation completes, open your repo in GitHub and you should see a message indicating a recently pushed branch.
You can view your changes by opening the `Branch: master` dropdown and selecting your new branch. Congratulations, you can share the branch URL with the world to show your progress!
-
+
## Submit your changes for review
@@ -117,11 +117,11 @@ At this point you have completed your change but it still only resides in your r
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -129,28 +129,12 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share).
You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-
-### [Additional material](additional-material/git_workflow_scenarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
-
-|
|
|
|
|
|
|
-|---|---|---|---|---|---|
-|[Command Line](README.md)|[GitHub Desktop](github-desktop-tutorial.md)|[GitKraken](gitkraken-tutorial.md)|[Visual Studio Code](github-windows-vs-code-tutorial.md)|[Atlassian Sourcetree](sourcetree-macos-tutorial.md)|[IntelliJ IDEA](github-windows-intellij-tutorial.md)|
-
-
-
-## Self-Promotion
-
-If you liked this project, star it on [GitHub](https://github.com/Roshanjossey/first-contributions).
-If you're feeling especially charitable, follow [Roshan](https://roshanjossey.github.io/) on
-[Twitter](https://twitter.com/sudo__bangbang) and
-[GitHub](https://github.com/roshanjossey).
-
-
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/gitkraken-tutorial.md b/gui-tool-tutorials/gitkraken-tutorial.md
similarity index 56%
rename from gitkraken-tutorial.md
rename to gui-tool-tutorials/gitkraken-tutorial.md
index cf6bdd55b54..b3df9a7adab 100644
--- a/gitkraken-tutorial.md
+++ b/gui-tool-tutorials/gitkraken-tutorial.md
@@ -1,12 +1,12 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
-|
|GitKraken Edition|
+|
|GitKraken Edition|
|---|---|
It's hard. It's always hard, when you do something for the first time. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time.
@@ -22,7 +22,7 @@ Download [GitKraken](https://www.gitkraken.com), Install and open it.
You should see the "Welcome to GitKraken" modal dialog - Sign in with GitHub and allow GitKraken access to your GitHub account.
-
+
(optional) Go to File -> Preferences and set your project directory to the root of your local repositories.
@@ -30,7 +30,7 @@ You should see the "Welcome to GitKraken" modal dialog - Sign in with GitHub and
## Fork this repository
Fork this repo by clicking on the fork button on the top of this page.
-
+
This will create of copy of this repository in your account.
@@ -39,7 +39,7 @@ This will create of copy of this repository in your account.
In GitKraken, go to File -> Clone Repo.
-
+
Select GitHub.com in the right pane. Under your username, you should see first-contributions. Click that repository and check the full path shown at the bottom of this pane.
@@ -53,7 +53,7 @@ Click the branch button on the toolbar.
Name your branch "add-your-name", for example: "add-william-sutton"
-
+
## Make necessary changes and commit those changes
@@ -62,18 +62,18 @@ Now open `Contributors.md` file in a text editor and add your name to it, then s
If you have the repo open in GitKraken you'll see there are changes. Review and stage those changes by selecting the newest commit marked with "// WIP" and the number of files changed and the type of change.
-
+
Review the files that have been changed and decide what you would like to stage. Staging is important to tell git exactly what file changes you want associated with this commit.
-
+
Once you have a good commit message ("Add to Contributors list" sounds nice and descriptive) and are happy with your changes, you can hit "Stage all changes" to stage everything that is modified or "Stage File" to stage an individual file.
-
+
If you change your mind, you can unstage those changes, or you can discard them all together.
@@ -86,11 +86,11 @@ Congratulations, you've committed all the changes to your local copy of your bra
## Push changes to GitHub
-
+
Click the Push button on the toolbar.
-
+
Submit changes on the origin branch if you want the changes to reflect in the master branch directly, else select the appropriate branch you want to push.
@@ -99,11 +99,11 @@ Submit changes on the origin branch if you want the changes to reflect in the ma
If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -111,26 +111,13 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io/first-contributions/#social-share).
You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-### [Additional material](additional-material/git_workflow_senarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_senarios/additional-material.md)
## Tutorials Using Other Tools
-
-|
|
|
|
|
|
|
-|---|---|---|---|---|---|
-|[Command Line](README.md)|[GitHub Desktop](github-desktop-tutorial.md)|[Visual Studio 2017](github-windows-vs2017-tutorial.md)|[Visual Studio Code](github-windows-vs-code-tutorial.md)|[Atlassian Sourcetree](sourcetree-macos-tutorial.md)|[IntelliJ IDEA](github-windows-intellij-tutorial.md)|
-
-## Self-Promotion
-
-If you liked this project, star it on [GitHub](https://github.com/Roshanjossey/first-contributions).
-If you're feeling especially charitable, follow [Roshan](https://roshanjossey.github.io/) on
-[Twitter](https://twitter.com/sudo__bangbang) and
-[GitHub](https://github.com/roshanjossey).
-
-
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/sourcetree-macos-tutorial.md b/gui-tool-tutorials/sourcetree-macos-tutorial.md
similarity index 62%
rename from sourcetree-macos-tutorial.md
rename to gui-tool-tutorials/sourcetree-macos-tutorial.md
index 92e6dfd72f7..84c29bdd94e 100644
--- a/sourcetree-macos-tutorial.md
+++ b/gui-tool-tutorials/sourcetree-macos-tutorial.md
@@ -1,12 +1,12 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
-|
|Atlassian Sourcetree|
+|
|Atlassian Sourcetree|
|---|---|
It's hard. It's always hard, when you do something for the first time. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time.
@@ -29,22 +29,22 @@ Download [Sourcetree](https://www.sourcetreeapp.com), Install and open it.
You should see the "Sourcetree" modal dialog.
-
+
From here, you want to click on Remote. If this is the first installation, then you likely haven't connected your GitHub account yet. Do so by clicking the "Connect Button".
-
+
The *Accounts* dialog will appear. Click "Add" in the lower left hand corner. Then select the appropriate settings to add GitHub (or any other account you want) to the client. After you selected your settings for GitHub, click "Connect Account."
-
+
This will open a page in your web browswer. Follow the steps given to authorize your account.
## Fork this repository
Fork this repo by clicking on the fork button on the top of this page.
-
+
This will create of copy of this repository in your account.
@@ -52,11 +52,11 @@ This will create of copy of this repository in your account.
In Sourcetree, Click on the "Remote" button. This should load all of your GitHub repos which are listed on GitHub.
-
+
Once you click the "Clone" button, you will be presented with another view to define several different things.
-
+
1) **Source URL:** This is automatically filled and you dont need to change it. It is the URL from where your GitHub project resides.
@@ -78,7 +78,7 @@ Name your branch "add-your-name-to-contribution", for example: "add-sally-to-con
To do this, click **Branch (1)** which launches the naming dialog. Then **Add your name (2)** as just described. Finally click **Create Branch**. This will create the branch for what you just named.
-
+
## Make necessary changes and commit those changes
@@ -89,7 +89,7 @@ You should be able to see and review the file that have been changed and decide
*Note: If you do not see the file's diff, click **Uncommitted Files** at the top of your dialog*
-
+
Next click the **Commit** button on the top left of the dialog. This will show you your staging area.
@@ -97,7 +97,7 @@ Click the *Checkbox* to **add** the file to the stagging area. Then enter a comm
*Note: You can also select files (both in the stagging and unstaged areas) and add/remove files from the respective areas by using the spacebar*
-
+
Once you have added your changes and added a commit message, you can press the **Commit** button to finally make the commit.
@@ -109,17 +109,17 @@ Congratulations, you've committed all the changes to your local copy of your bra
Now you are ready to push your changes to github. This will be pushing it to your own, forked, copy of the project. Follow the steps to push your branch up. First, click **Push (1)**, this will show the remote/push dialog. **Click (2)** the checkbox of your branch you want to push. Select **OK (3)** and this will push your commit up to Github.
-
+
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -127,26 +127,13 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io/first-contributions/#social-share).
You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-### [Additional material](additional-material/git_workflow_senarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_senarios/additional-material.md)
## Tutorials Using Other Tools
-
-|
|
|
|
|
|
|
-|---|---|---|---|---|---|
-|[Command Line](README.md)|[GitHub Desktop](github-desktop-tutorial.md)|[Visual Studio 2017](github-windows-vs2017-tutorial.md)|[GitKraken](gitkraken-tutorial.md)|[Visual Studio Code](github-windows-vs-code-tutorial.md)|[IntelliJ IDEA](github-windows-intellij-tutorial.md)|
-
-## Self-Promotion
-
-If you liked this project, star it on [GitHub](https://github.com/Roshanjossey/first-contributions).
-If you're feeling especially charitable, follow [Roshan](https://roshanjossey.github.io/) on
-[Twitter](https://twitter.com/sudo__bangbang) and
-[GitHub](https://github.com/roshanjossey).
-
-
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/sublime-merge-tutorial.md b/gui-tool-tutorials/sublime-merge-tutorial.md
similarity index 62%
rename from sublime-merge-tutorial.md
rename to gui-tool-tutorials/sublime-merge-tutorial.md
index 35ea1d99227..89bd4764418 100644
--- a/sublime-merge-tutorial.md
+++ b/gui-tool-tutorials/sublime-merge-tutorial.md
@@ -1,12 +1,12 @@
[](https://github.com/ellerbrock/open-source-badges/)
-[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
+[
](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[](https://opensource.org/licenses/MIT)
[](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
-|
|Sublime Merge Git Client|
+|
|Sublime Merge Git Client|
|---|---|
It's hard. It's always hard, when you do something for the first time. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time.
@@ -21,18 +21,18 @@ Download [Sublime Merge](https://www.sublimemerge.com/), Install and open it.
## Fork this repository
Fork this repo by clicking on the fork button on the top of this page.
-
+
This will create of copy of this repository in your account.
## Clone the repository
-
+
In Sublime Merge, go to File -> Clone Repository.
-
+
The next step is to clone your repo down to your machine so you can begin making changes. Sublime Merge needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon.
@@ -52,7 +52,7 @@ Navigate to Repository -> Create Branch
Name your branch "add-your-name", for example: "add-william-sutton"
-
+
## Make necessary changes and commit those changes
@@ -65,7 +65,7 @@ Review the files that have been changed and decide what you would like to stage.
Give the commit a commit message ("Add to Contributors list" sounds nice and descriptive).
When you are happy with your changes stage those changes by staging them file by file or selecting "stage all". Staging is important to tell git exactly what file changes you want associated with this commit.
-
+
If you change your mind, you can unstage those changes, or you can discard them all together.
WARNING: As the word discard implies, this is a destructive operation. Do this only if you don't want any change(s) from whatever repository you're in.
@@ -82,7 +82,7 @@ Congratulations, you've committed all the changes to your local copy of your bra
Navigate to Repository -> Push
or hit the small arrow in upward direction in the right hand corner.
-
+
Login to your Github Account with your username and password
@@ -93,11 +93,11 @@ Submit changes on the origin branch if you want the changes to reflect in the ma
If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button.
-
+
Now submit the pull request.
-
+
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
@@ -105,17 +105,13 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
-Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
+Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share).
You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
-Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).
-### [Additional material](additional-material/git_workflow_senarios/additional-material.md)
+### [Additional material](../additional-material/git_workflow_senarios/additional-material.md)
## Tutorials Using Other Tools
-
-|
|
|
|
|
|
|
-|---|---|---|---|---|---|
-|[Command Line](README.md)|[GitHub Desktop](github-desktop-tutorial.md)|[Visual Studio 2017](github-windows-vs2017-tutorial.md)|[Visual Studio Code](github-windows-vs-code-tutorial.md)|[Atlassian Sourcetree](sourcetree-macos-tutorial.md)|[IntelliJ IDEA](github-windows-intellij-tutorial.md)|
+[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
\ No newline at end of file
diff --git a/package-lock.json b/package-lock.json
deleted file mode 100644
index 48e341a0954..00000000000
--- a/package-lock.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
- "lockfileVersion": 1
-}