lucasvbr/first-contributions
1
0
Fork 0
mirror of https://github.com/LucasVbr/first-contributions.git synced 2026-05-13 17:21:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

reset repo

Browse Source
This commit is contained in:
Roshanjossey
2025-01-03 22:30:04 +01:00
commit b166a1d130
314 changed files with 31890 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gui-tool-tutorials/github-desktop-old-version-tutorial.md
+108
View File
@@ -0,0 +1,108 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
|<img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200">|GitHub Desktop Edition|
|---|---|
It's hard. It's always hard the first time you do something. 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.
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.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/fork.png" alt="fork this repository" />
If you don't have GitHub Desktop on your machine, [install it](https://desktop.github.com/).
## 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
Now clone this repo to your machine.
Open the GitHub Desktop app and click on the `+` on the top left.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-clone1.png" alt="clone this repository" />
If it is not already selected, click on `Clone`. Then choose first-contributions and then click on `Clone first-contributions`
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-clone2.png" alt="clone this repository" />
Choose the directory on your machine you would like to clone first-contributions into
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-clone3.png" alt="clone this repository" />
Now you have copied the contents of the first-contributions repository in github to your computer.
## Create a branch
Now create a branch by clicking on the branch icon at the top left:
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-branch1.png" alt="make a branch" />
Name your branch add-your-name. For example, add-crawleya
Click on `Create new branch`
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-branch2.png" alt="name your branch" />
## Make necessary changes and commit those changes
Now open `Contributors.md` file in a text editor and add your name to it, then save the file.
You can see that there are changes to Contributors.md and they have been added.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-status.png" alt="check status" />
Now commit those changes:
Write the message "Add `<your-name>` to Contributors list" in the *summary* field
Replace `<your-name>` with your name
Click on the button that says `Commit to add-your-name`
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-commit1.png" alt="commit your changes" />
At the bottom, you can see that the commit has been created.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-commit2.png" alt="commit your changes" />
## Push changes to github
Click the `Publish` button on the top right.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/dt-publish1.png" alt="push your changes" />
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. click on that button.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_senarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/github-desktop-tutorial.md
+118
View File
@@ -0,0 +1,118 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
It's hard. It's always hard the first time you do something. 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.
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/).
If you're using a version of GitHub desktop before 1.0, [refer to this tutorial](github-desktop-old-version-tutorial.md).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## 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 account.
## Clone the repository
Now clone this repo to your machine.
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".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
A pop up window will open. Click on "Open GitHubDesktop.exe".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
After you click on "Open GitHubDesktop.exe" the contents will be downloaded to your computer.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
Now you have copied the contents of the first-contributions repository in github to your computer.
## Create a branch
Now create a branch by clicking on the "Current branch" icon at the top and then click on "New branch":
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="make a branch" />
Name your branch <add-your-name>. For example, "add-james-smith"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
Click on `Create branch`
## Make necessary changes and commit those changes
Now, go to history tab and open `Contributors.md` file in a text editor by right clicking and open in text editor. Scroll to the bottom of the page and add your name to it, then save the file.
Example: If your name is James Smith, It should look like this.
\[James Smith](https://github.com/jamessmith)
You can see that there are changes to Contributors.md and they have been added to the Github Desktop.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
Now commit those changes:
Write the message "Add `<your-name>` to Contributors list" in the _summary_ field.
Replace `<your-name>` with your name.
Click on the button that says `Commit to add-your-name`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
At the bottom, you can see that the commit has been created.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit your changes" />
## Push changes to github
Click on File->Options and sign-in to Github.com. Type in your Github username and password.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in to Github" />
Click the `Publish` button on the top right.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push your changes" />
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. click on that button.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/github-windows-intellij-tutorial.md
+112
View File
@@ -0,0 +1,112 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
| <img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/9/9c/IntelliJ_IDEA_Icon.svg" width="40"> | Intellij IDEA |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
It's hard. It's always hard the first time you do something. 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.
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 IntelliJ IDEA on your machine, [install it](https://www.jetbrains.com/idea/download/#section=windows).
**Notice:** This tutorial was made using IntelliJ IDEA (Version 2019.3.2) on a Windows 10 machine. Later in this tutorial we will make use of some keyboard shortcuts. These may differ on other operating systems (macOS/Linux).
## Fork this repository
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="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.
GitHub keeps track of the relationship between your repo and the one you have forked it from. You can think of your repo as a working copy.
Most top-level GitHub Repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes. All other contributors must fork the repo and make changes in the fork, then create a Pull Request to request to merge back their changes into the top-level repo. If the top-level repo administrator approves the changes they will be merged, and you will gain instant fame and fortune! More on how to do that later.
## Clone your repository
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this 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.
**CAREFUL:** One common mistake that new contributors often make is to clone the repo you forked _from_ rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo.
Now open up IntelliJ IDEA.
IntelliJ IDEA allows you to check out (in Git terms clone) an existing repository and create a new project based on the data you've downloaded.
From the main menu, choose VCS | Get from Version Control, or, if no project is currently opened, click Get from Version Control on the Welcome screen.
In the Get from Version Control dialog, specify the URL of the remote repository you want to clone (you can click Test to make sure that connection to the remote can be established) or select one of the VCS hosting services on the left. If you are already logged in to the selected hosting service, completion will suggest the list of available repositories that you can clone.
Click Clone. If you want to create an IntelliJ IDEA project based on the sources you have cloned, click Yes in the confirmation dialog. Git root mapping will be automatically set to the project root directory.
If your project contains submodules, they will also be cloned and automatically registered as project roots.
**Important**: Make sure it is the forked repository and not the original one, otherwise it won't work.
## Create a branch
In Git, branching is a powerful mechanism that allows you to diverge from the main development line, for example, when you need to work on a feature or freeze a certain state of a codebase for a release, and so on.
In IntelliJ IDEA, all operations with branches are performed in the Git Branches popup. To invoke it, click the Git widget in the Status bar or press Ctrl+Shift+`.
The name of the branch that is currently checked out is displayed in the Git widget in the Status bar.
In the branches popup, choose New Branch.
In the dialog that opens, specify the branch name, and make sure the Checkout branch option is selected if you want to switch to that branch.
The new branch will start from the current HEAD. If you want to start a branch from a previous commit instead of the current branch HEAD, select this commit in the Log tab of the Version Control tool window Alt+9 and choose New Branch from the context menu.
## Make necessary changes
Open `Contributors.md` and add your name anywhere in the file. This file contains GFM (GitHub Flavored Markdown) which is a proprietary flavor of the <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a> syntax.
Copy one of the other contributors&apos; lines and modify it with your name to make sure you get the syntax right - it can be picky.
## Commit & Push changes to GitHub
Select the files you want to commit or an entire changelist in the Local Changes tab of the Version Control tool window Alt+9 and press Ctrl+K or click Commit Commit button on the toolbar.
The Commit Changes dialog that opens lists all files that have been modified since the last commit, as well as all newly added unversioned files.
Enter a meaningful commit message.
You can click Commit Message history Commit Message history Ctrl+M to choose from the list of recent commit messages.
You can also edit the commit message later before you've pushed the commit.
Press Ctrl+Shift+K or choose VCS | Git | Push from the main menu. The Push Commits dialog opens showing all Git repositories (for multi-repository projects) and listing all commits made in the current branch in each repository since the last push.
## Submit your changes for review
At this point you have completed your change but it still only resides in your repo. This step will show you how to submit a request to the administrator of the top-level repo to merge your change.
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/github-windows-vs-code-tutorial.md
+118
View File
@@ -0,0 +1,118 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
It's hard. It's always hard the first time you do something. 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.
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 Visual Studio Code on your machine, [install it](https://code.visualstudio.com/download).
**Notice:** This tutorial was made using Visual Studio Code (Version 1.27.2) on a Windows 10 machine. Later in this tutorial we will make use of some keyboard shortcuts. These may differ on other operating systems (macOS/Linux) as well as keyboard language (UK, DE, etc). You can go through your list of shortcuts by searching "shortcut" in the Command Palette.
## Fork this repository
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="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.
GitHub keeps track of the relationship between your repo and the one you have forked it from. You can think of your repo as a working copy.
Most top-level GitHub repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes. All other contributors must fork the repo and make changes in the fork, then create a Pull Request to ask for their changes to be merged back into the top-level repo. If the top-level repo administrator likes the changes they will be merged and you will gain instant fame and fortune! More on how to do that later.
## Clone your repository
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this 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 code button and then click the "copy to clipboard" icon.
**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked _from_ rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo.
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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Now type in `git clone`, only `git` or `clone` (it works like a search).
Select the Entry `Git: Clone` and press `Enter`
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
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.
## Create a branch
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)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Make necessary changes
Open `Contributors.md` and add your name anywhere in the file. This file contains GFM (GitHub Flavored Markdown) which is a proprietary flavor of the <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a> syntax.
Copy one of the other contributors&apos; lines and modify it with your name to make sure you get the syntax right - it can be picky. Save file to register change.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## 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)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## Submit your changes for review
At this point you have completed your change but it still only resides in your repo. This step will show you how to submit a request to the administrator of the top-level repo to merge your change.
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/github-windows-vs2017-tutorial.md
+140
View File
@@ -0,0 +1,140 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
|<img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/61/Visual_Studio_2017_logo_and_wordmark.svg/2000px-Visual_Studio_2017_logo_and_wordmark.svg.png" width="200">|Visual Studio 2017 Edition|
|---|---|
It's hard. It's always hard the first time you do something. 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.
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 Visual Studio 2017 on your machine, [install it](https://www.visualstudio.com/downloads/).
## Fork this repository
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/fork.png" alt="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.
GitHub keeps track of the relationship between your repo and the one you forked it from. You can think of your repo as a working copy.
Most top-level GitHub repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes. All other contributors must fork the repo and make changes in the fork, then create a Pull Request to ask for their changes to be merged back into the top-level repo. If the top-level repo administrator likes the changes they will be merged and you will gain instant fame and fortune! More on how to do that later.
## Clone your repository
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/clone.png" alt="clone this 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.
**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked *from* rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo.
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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-01-clone1.png" alt="Team Explorer" />
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.
Click the `Clone` option under **Local Git Repositories** and paste the URL to your repo in the text box. This should be the URL you copied to your clipboard from GitHub previously.
Click the `Clone` button to initiate the process.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-02-clone2.png" alt="Clone repo" />
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!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-03-clone3.png" alt="Solution Explorer" />
## Create a branch
Click back to the Team Explorer tab and use the main navigation dropdown to open the Branches view.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-04-branch1.png" alt="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...`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-05-branch2.png" alt="New branch" />
Give your branch a name like `add-<your_name_here>`, for example: `add-alonzo-church`.
Leave the `Checkout branch` box checked and click the `Create Branch` button.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-06-branch3.png" alt="Create branch" />
You should see your new branch in the list.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-07-branch4.png" alt="See new branch" />
## Make necessary changes
Open `Contributors.md` and add your name to the end of the list. This file contains GFM (GitHub Flavored Markdown) which is a proprietary flavor of the <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a> syntax.
Copy one of the other contributors&apos; lines and modify it with your name to make sure you get the syntax right - it can be picky.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-08-change1.png" alt="Add your name" />
## Commit & Push changes to GitHub
Switch back to Team Explorer and navigate to the Changes view.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-09-commit1.png" alt="Changes" />
Enter the information you want to post with your commit and click `Save`. Visual Studio will remember it for future commits.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-10-commit2.png" alt="Git user information" />
**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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-11-commit3.png" alt="Ignore vs folder" />
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!
Click `Commit All and Push` to perform a local commit and push your changes back up to your repo, all in one step.
**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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-12-commit4.png" alt="Commit and 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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-13-commit5.png" alt="Login" />
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!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-14-commit6.png" alt="View pushed branch on GitHub" />
## Submit your changes for review
At this point you have completed your change but it still only resides in your repo. This step will show you how to submit a request to the administrator of the top-level repo to merge your change.
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/gitkraken-tutorial.md
+123
View File
@@ -0,0 +1,123 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
|<img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="200">|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.
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.
## Git Kraken
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.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(optional) Go to File -> Preferences and set your project directory to the root of your local repositories.
## Fork this repository
Fork this repo by clicking on the fork button on the top of this page.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="fork this repository" />
This will create of copy of this repository in your account.
## Clone the repository
In GitKraken, go to File -> Clone Repo.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
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.
Once you're satisfied with the path, click "Clone the repo!".
## Create a branch
Click the branch button on the toolbar.
Name your branch "add-your-name", for example: "add-william-sutton"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## Make necessary changes and commit those changes
Now open `Contributors.md` file in a text editor and add your name to it, then save the file.
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.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
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.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
Once you have a good commit message ("Add <your-name> 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.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
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.
Hit commit.
Congratulations, you've committed all the changes to your local copy of your branch of your fork of first-contributions. Onward!
## Push changes to GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
Click the Push button on the toolbar.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
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.
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/sourcetree-macos-tutorial.md
+139
View File
@@ -0,0 +1,139 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
|<img alt="SourceTree" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-logo.png" width="200">|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.
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.
## Sourcetree
Please note, this tutorial is for MacOS. It is similar to Sourcetree on Windows but some things may look different.
<!--
****************************************
*** This is commented out until ***
*** a Windows tutorial can be created***
****************************************
Please note, this tutorial is for MacOS. Please refer to the [Windows Tutorial]() for Sourcetree if that is what you want to use.
-->
Download [Sourcetree](https://www.sourcetreeapp.com), Install and open it.
You should see the "Sourcetree" modal dialog.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-1-main.png" alt="SourceTree Main" />
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".
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-2-main-connect.png" alt="SourceTree Connect" />
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."
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-4-accounts-add.png" alt="SourceTree Connect Add" />
This will open a page in your web browser. 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.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/fork.png" alt="fork this repository" />
This will create of copy of this repository in your account.
## Clone the repository
In Sourcetree, Click on the "Remote" button. This should load all of your GitHub repos which are listed on GitHub.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-5-cloning.png" alt="clone this repository" />
Once you click the "Clone" button, you will be presented with another view to define several different things.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-6-cloning-confirm.png" alt="clone this repository" />
1) **Source URL:** This is automatically filled and you don't need to change it. It is the URL from where your GitHub project resides.
2) **Destination Path:** This is the physical location on your computer where this project will be saved
3) **Name:** This is a "Bookmark" to how Sourcetree will reference your project. Think of it like a shortcut.
*Note: Normally the defaults in these fields are fine.*
**Once you are satisfied, click "Clone"**
This will bring up the main repo browser for your repository!
## Create a branch
Click the branch button on the toolbar.
Name your branch "add-your-name-to-contribution", for example: "add-sally-to-contribution".
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.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-7-branching.png" alt="name your branch" />
## Make necessary changes and commit those changes
Now open `Contributors.md` file in a text editor and add your name to it, with your Github URL link, then save the file.
You should be able to see and review the file 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.
*Note: If you do not see the file's diff, click **Uncommitted Files** at the top of your dialog*
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-8-viewing-changed-files.png" alt="edit some file(s)" />
Next click the **Commit** button on the top left of the dialog. This will show you your staging area.
Click the *Checkbox* to **add** the file to the staging area. Then enter a commit message.
*Note: You can also select files (both in the staging and unstaged areas) and add/remove files from the respective areas by using the spacebar*
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-9-committing.png" alt="stage your changes" />
Once you have added your changes and added a commit message, you can press the **Commit** button to finally make the commit.
Congratulations, you've committed all the changes to your local copy of your branch of your fork of first-contributions. Onward!
## Push changes to GitHub
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.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-10-pushing.png" alt="origin or branch" />
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/sublime-merge-tutorial.md
+121
View File
@@ -0,0 +1,121 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
|<img alt="Sublime Merge" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sublime-merge.png" width="200">|Sublime Merge Git Client|
|---|---|
It's hard. It's always hard, when you do something for the first time. Especially when you are collaborating or trying out something new, 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.
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.
## Sublime Merge
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.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/fork.png" alt="fork this repository" />
This will create of copy of this repository in your account.
<br>
<br>
<br>
<br>
## Clone the repository
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/clone.png" alt="clone this repository" />
In Sublime Merge, go to File -> Clone Repository.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-clone.png" alt="clone this 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.
**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked _from_ rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo.
Enter the URL of the repo in Sublime Merge, give it a repository name (or leave it blank) and set your directory where to save the repository.
Once you're satisfied with the path, click "Clone".
## Create a branch
Right click Branches -> Create Branch
or
Navigate to Repository -> Create Branch
Name your branch "add-your-name", for example: "add-william-sutton"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-branch.png" alt="name your branch" />
## Make necessary changes and commit those changes
Now open `Contributors.md` file in a text editor and add your name to it, then save the file.
If you have the repo open in Sublime Merge you'll see there are changes.
Select the newest commit at the top, named "x unstaged files"
Review the files that have been changed and decide what you would like to stage.
Give the commit a commit message ("Add <your-name> 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.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-stage.png" alt="stage your changes" />
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.
Hit commit and enter your username and email address and press Update.
Hit commit again.
Congratulations, you've committed all the changes to your local copy of your branch of your fork of first-contributions. Onward!
## Push changes to GitHub
Navigate to Repository -> Push
or hit the small arrow in upward direction in the right hand corner.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-login.png" alt="login" />
Login to your Github Account with your username and password
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.
## Submit your changes for review
If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/submit-pull-request.png" alt="submit 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.
## Where to go from here?
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://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/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Additional material](../additional-material/git_workflow_senarios/additional-material.md)
## Tutorials Using Other Tools
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Chinese/github-desktop-tutorial.zh-cn.md
+117
View File
@@ -0,0 +1,117 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# 第一次贡献
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
万事开头难。特别是当你正与其他人合作的时侯，出错不是一件舒服的事情。不过，开源的本质就是和他人合作。我们想要简化开源初学者第一次学习和贡献的方法。
你可以通过阅读文章和观看教程来得到帮助，但是没有比实际去做而不搞砸更好的方法了。本项目旨在简化并指导初学者参与他们的第一次开源。记住：过程越轻松，学习效益越高。如果你想要做出第一次贡献，只需按照以下简单步骤操作即可。相信我们，这将会是一个有趣的过程 :)
如果你没有GithubDesktop在你的电脑上, [点我安装](https://desktop.github.com/).
如果你使用的是1.0之前的GitHub Desktop版本, [请参阅本教程](github-desktop-old-version-tutorial.md).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## Fork（复制）本代码仓库
点击页面顶部的 “Fork” 按钮来分叉（Fork）这个仓库。这将在你的账户中创建这个存储库的副本。
## Clone（克隆）代码仓库
现在将这个储存库复制到你的电脑。
重要！：不要复制源储存库。请到自己的仓库并复制
要克隆仓库，请单击“Clone or Download”，然后单击“Open in Desktop”。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
一个弹出窗口将会打开。点击“打开GitHubDesktop.exe”。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
点击“打开GitHubDesktop.exe”后，内容将下载到您的计算机上。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
现在，您已经将github中first-contributions存储库的内容复制到了您的计算机上。
## 创建分支
现在，点击顶部的“Current branch”图标，然后点击“New branch”，即可创建分支：
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="make a branch" />
命名你的分支<添加你的名字>。例如，“add-james-smith”
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
点击 `Create branch`
## 进行必要的更改并提交这些更改
现在，转到历史记录选项卡，右键单击并在文本编辑器中打开文本编辑器中的“Contributors.md”文件。滚动到页面底部并添加您的姓名，然后保存文件。
例子: 如果你的名字是 James Smith, 它因该看起来像这样.
\[James Smith](https://github.com/jamessmith)
您可以看到对Contributors.md进行了更改，并且已将其添加到GithubDesktop。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
现在提交这些更改：
在_summary_字段中写下消息“Add `<你的名字>`to Contributors list”。
将“<你的名字>”替换为你的名字。
点击按钮，上面写着 `Commit to add-your-name`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
在底部，您可以看到提交已创建。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit your changes" />
## 将更改推送到github
点击文件->选项，登录Github.com。输入您的Github用户名和密码.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in to Github" />
点击右上角的“Publish”按钮。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push your changes" />
## 提交您的更改以供审核
如果你去github上的仓库，你会看到“Compare & pull request”按钮。点击那个按钮。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
现在提交拉取请求.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
很快，我将把您的所有更改合并到这个项目的主分支中。合并更改后，您将收到一封通知电子邮件。
## 下一步我该去哪里？
恭喜！您刚刚完成了作为贡献者经常遇到的标准_fork->clone->edit->PR_工作流程！
庆祝你的贡献，并通过以下方式与你的朋友和追随者分享[web app](https://firstcontributions.github.io#social-share).
如果您需要帮助或有任何问题，可以加入我们的slack team. [加入 slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [附加材料](../additional-material/git_workflow_scenarios/additional-material.md)
## 使用其他工具的教程
[返回主页](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Chinese/gitkraken-tutorial-zh-cn.md
+108
View File
@@ -0,0 +1,108 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# 第一次参与开源项目
| <img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="200"> | GitKraken 版 |
| ------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
万事开头难。特别是当你正与其他人合作的时侯，出错不是一件舒服的事情。不过，开源的本质就是和他人合作。我们想要简化开源初学者第一次学习和贡献的方法。
你可以通过阅读文章和观看教程来得到帮助，但是没有比实际去做而不搞砸更好的方法了。本项目旨在简化并指导初学者参与他们的第一次开源。记住：过程越轻松，学习效益越高。如果你想要做出第一次贡献，只需按照以下简单步骤操作即可。相信我们，这将会是一个有趣的过程 :)
## Git Kraken
下载[GitKraken](https://www.gitkraken.com)，安装并打开它。
你应该会看到 "Welcome to GitKraken" 的对话框。
使用你的GitHub账号登陆并允许GitKraken 访问你的 GitHub 账户。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(可选)点击文件“File” ，选择首选项“Preferences”，将你的项目目录设置为本地存储库的根目录。
## Fork（复制）本代码仓库
点击页面顶部的 “Fork” 按钮来分叉（Fork）这个仓库。<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="fork this repository" />
这将在你的账户中创建这个存储库的副本。
## Clone（克隆）代码仓库
在GitKraken中，点击文件“File” ，选择克隆储存库。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
在右侧窗格中选择 ”GitHub.com“。在你的用户名下，你应该看到 “first-contributions”。点击该存储库并查看窗格底部显示的完整路径。
当你确定你想要保存在本地的路径后，点击 “Clone the repo!”。
## 新建一个代码分支
点击工具栏上的 "分支"（Branch）按钮。
给你的分支命名为 "add-your-name"，例如："add-william-sutton"。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## 进行必要的更改并提交这些更改
现在在文本编辑器中打开`Contributors.md`文件并添加您的名字，然后保存文件。
如果你在 GitKraken 中打开了存储库，你会看到有更改。请通过选择最新的提交（标有“// WIP”以及更改的文件数和更改的类型）来审查和暂存这些更改。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
审查已更改的文件，并决定哪些文件你想要暂存。暂存很重要，它告诉 Git 哪些文件更改与这次提交相关。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
一旦你有了一个不错的提交消息（比如“将 <你的名字> 添加到贡献者列表”，这听起来不错而且描述清楚），并且对你的更改感到满意，你可以点击“暂存所有更改”来暂存所有已修改的内容，或者点击“暂存文件”来暂存单个文件。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
如果你改变主意，你可以取消这些更改，或者将它们全部丢弃。
警告：由于"discard"（丢弃）这个词的含义，这是一种破坏性的操作。只有当你不希望保留你所在的仓库中的任何更改时才执行此操作。
点击 commit（提交）
恭喜！你已将所有更改提交到首次贡献分支的本地副本。继续前进吧！
## 将改动 Push（推送）到 GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
点击工具栏上的 "Push" 按钮。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
如果你想要更改直接反映在主分支中，就提交更改到源分支。否则，选择你想要推送的适当分支。
## 提交你的更改供他人审阅
如果你在 GitHub 上进入你的存储库，你会看到`Compare & pull request`按钮。点击这个按钮。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
现在提交拉取请求。
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit pull request" />
很快我将把你的所有更改合并到这个项目的主分支中。一旦更改已经合并，你将收到通知邮件。
## 接下来该做什么呢？
恭喜！你刚刚完成了作为贡献者经常遇到的标准“分叉 -> 克隆 -> 编辑 -> 提交请求（PR）”的工作流程！
庆祝你的贡献，并通过前往[web app](https://firstcontributions.github.io/#social-share)分享给你的朋友和关注者。
如果有任何疑问或想获得更多协助，欢迎加入我们的 [Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)！
### [更多资料](../additional-material/git_workflow_scenarios/additional-material.md)
## 使用其他工具的教程
[返回主页](https://github.com/firstcontributions/first-contributions/blob/main/translations/README.zh-cn.md)
docs/gui-tool-tutorials/translations/Greek/github-desktop-old-version-tutorial.gr.md
+80
View File
@@ -0,0 +1,80 @@
[![Αγάπη για το Ανοικτό Κώδικα](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Άδεια: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Βοηθοί Ανοικτού Κώδικα](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
|<img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200">|Έκδοση GitHub Desktop|
|---|---|
Είναι δύσκολο. Είναι πάντα δύσκολο την πρώτη φορά που κάνετε κάτι. Ειδικά όταν συνεργάζεστε, το να κάνετε λάθη δεν είναι κάτι άνετο. Ωστόσο, ο ανοικτός κώδικας αφορά τη συνεργασία και την εργασία μαζί. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο νέοι συνεισφέροντες στον ανοικτό κώδικα μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Η ανάγνωση άρθρων και η παρακολούθηση μαθημάτων μπορεί να βοηθήσει, αλλά τι μπορεί να είναι καλύτερο από το να κάνετε πράγματι τα πράγματα χωρίς να κάνετε κάποιο λάθος. Αυτό το έργο στοχεύει στην παροχή καθοδήγησης και απλοποίησης του τρόπου με τον οποίο οι νέοι χρήστες κάνουν την πρώτη τους συνεισφορά. Θυμηθείτε, όσο πιο χαλαροί είστε, τόσο καλύτερα μαθαίνετε. Εάν θέλετε να κάνετε την πρώτη σας συνεισφορά, ακολουθήστε απλά τα απλά βήματα παρακάτω. Σας υποσχόμαστε ότι θα είναι διασκεδαστικό.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/fork.png" alt="fork this repository" />
Εάν δεν έχετε το GitHub Desktop στη μηχανή σας, [εγκαταστήστε το](https://desktop.github.com/).
## Κλωνοποίηση αυτού του αποθετηρίου
Κλωνοποιήστε αυτό το αποθετήριο κάνοντας κλικ στο κουμπί κλωνοποίησης στην κορυφή αυτής της σελίδας.
Αυτό θα δημιουργήσει ένα αντίγραφο αυτού του αποθετηρίου στον λογαριασμό σας.
## Κλωνοποίηση του αποθετηρίου
Τώρα κλωνοποιήστε αυτό το αποθετήριο στη μηχανή σας.
Ανοίξτε την εφαρμογή GitHub Desktop και κάντε κλικ στο `+` στην επάνω αριστερή γωνία.
Αν δεν είναι ήδη επιλεγμένο, κάντε κλικ στο `Κλωνοποίηση`. Στη συνέχεια, επιλέξτε το first-contributions και κάντε κλικ στο `Κλωνοποίηση first-contributions`.
Επιλέξτε τον κατάλογο στη μηχανή σας όπου θέλετε να κλωνοποιήσετε το first-contributions.
Τώρα έχετε αντιγράψει το περιεχόμενο του αποθετηρίου first-contributions από το GitHub στον υπολογιστή σας.
## Δημιουργία κλαδιού
Δημιουργήστε τώρα ένα κλαδί κάνοντας κλικ στο εικονίδιο κλαδιού στην επάνω αριστερή γωνία:
Ονομάστε το κλαδί σας add-your-name. Για παράδειγμα, add-crawleya
Κάντε κλικ στο `Δημιουργία νέου κλαδιού`
## Κάντε τις απαραίτητες αλλαγές και κάντε δεσμεύσεις
Ανοίξτε τώρα το αρχείο `Contributors.md` σε έναν επεξεργαστή κειμένου και προσθέστε το όνομά σας, στη συνέχεια αποθηκεύστε το αρχείο.
Μπορείτε να δείτε ότι υπάρχουν αλλαγές στο Contributors.md και έχουν προστεθεί.
Τώρα, κάντε δεσμεύσεις για αυτές τις αλλαγές:
Γράψτε το μήνυμα "Προσθήκη `<του-όνομά-σας>` στη λίστα συντελεστών" στο πεδίο *σύνοψη*
Αντικαταστήστε το `<του-όνομά-σας>` με το όνομά σας
Κάντε κλικ στο κουμπί που λέει `Δεσμεύσεις για προσθήκη του-όνομά-σας`
Στο κάτω μέρος, μπορείτε να δείτε ότι έχει δημιουργηθεί η δέσμευση.
## Στείλτε τις αλλαγές σας για αναθεώρηση
Εάν πηγαίνετε στο αποθετήριό σας στο GitHub, θα δείτε το κουμπί `Σύγκριση & αίτηση τραβήγματος`. κάντε κλικ σε αυτό το κουμπί.
Τώρα υποβάλετε το αίτημα τραβήγματος.
Σύντομα θα συγχωνεύσω όλες τις αλλαγές σας στο κύριο κλαδί αυτού του έργου. Θα λάβετε ένα email ειδοποίησης όταν οι αλλαγές έχουν συγχωνευτεί.
## Πού να πάτε από εδώ;
Συγχαρητήρια! Μόλις ολοκληρώσατε την τυπική διαδικασία _fork -> clone -> edit -> PR_ που συναντάτε συχνά ως συνεισφέρων!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε τη με τους φίλους σας και τους ακόλουθούς σας πηγαίνοντας στην [ιστοσελίδα εφαρμογής](https://firstcontributions.github.io#social-share).
Μπορείτε να εγγραφείτε στην ομάδα μας στο Slack αν χρειάζεστε βοήθεια ή έχετε οποιεσδήποτε ερωτήσεις. [Εγγραφή στην ομάδα Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Πρόσθετο υλικό](../additional-material/git_workflow_senarios/additional-material.md)
## Οδηγίες Χρήσης Άλλων Εργαλείων
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Greek/github-desktop-tutorial.gr.md
+113
View File
@@ -0,0 +1,113 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | Έκδοση GitHub Desktop |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
Είναι δύσκολο. Είναι πάντα δύσκολο όταν κάνετε κάτι για πρώτη φορά. Ειδικά όταν συνεργάζεστε, τα λάθη δεν είναι άνετα. Αλλά η ανοικτή πηγή αφορά τη συνεργασία και την εργασία από κοινού. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο νέοι συνεισφέροντες στην ανοικτή πηγή μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Η ανάγνωση άρθρων και η παρακολούθηση εκπαιδευτικών βίντεο μπορούν να βοηθήσουν, αλλά τίποτα δεν είναι καλύτερο από το να κάνετε τα πράγματα χωρίς να κάνετε κάποιο λάθος. Αυτό το έργο στοχεύει στην παροχή καθοδήγησης και στην απλοποίηση του τρόπου με τον οποίο οι αρχάριοι συνεισφέροντες κάνουν την πρώτη τους συνεισφορά. Θυμηθείτε ότι όσο πιο χαλαροί είστε, τόσο καλύτερα μαθαίνετε. Αν θέλετε να κάνετε την πρώτη σας συνεισφορά, ακολουθήστε απλώς τα απλά βήματα παρακάτω. Σας υποσχόμαστε ότι θα είναι διασκεδαστικό.
Εάν δεν έχετε το GitHub Desktop στον υπολογιστή σας, [εγκαταστήστε το](https://desktop.github.com/).
Εάν χρησιμοποιείτε μια έκδοση του GitHub Desktop πριν το 1.0, [ανατρέξτε σε αυτό το εγχειρίδιο](github-desktop-old-version-tutorial.md).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## Κλωνοποίηση αυτού του αποθετηρίου
Κλωνοποιήστε αυτό το αποθετήριο και εγκαταστήστε το στον υπολογιστή σας.
ΣΗΜΑΝΤΙΚΟ: ΜΗΝ ΚΛΩΝΟΠΟΙΕΙΤΕ ΤΟ ΑΡΧΙΚΟ ΑΠΟΘΕΤΗΡΙΟ. Πηγαίνετε στο δικό σας δικλωνισμό και κλωνοποιήστε το.
Για να κλωνοποιήσετε το αποθετήριο, κάντε κλικ στο "Κλωνοποίηση ή Λήψη" και στη συνέχεια κάντε κλικ στο "Άνοιγμα στο Desktop".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
Θα ανοίξει ένα αναδυόμενο παράθυρο. Κάντε κλικ στο "Άνοιγμα GitHubDesktop.exe".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
Αφού κάνετε κλικ στο "Άνοιγμα GitHubDesktop.exe", τα περιεχόμενα θα ληφθούν στον υπολογιστή σας.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
Τώρα έχετε αντιγράψει τα περιεχόμενα του αποθετηρίου first-contributions στο GitHub στον υπολογιστή σας.
## Δημιουργία κλαδιού
Τώρα δημιουργήστε ένα κλαδί κάνοντας κλικ στο εικονίδιο "Τρέχον κλαδί" στο πάνω μέρος και στη συνέχεια κάντε κλικ στο "Νέο κλαδί":
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="make a branch" />
Ονομάστε το κλαδί σας <προσθέστε-το-όνομά-σας>. Για παράδειγμα, "προσθήκη-james-smith"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
Κάντε κλικ στο `Δημιουργία κλαδιού`
## Κάντε τις απαραίτητες αλλαγές και καταγράψτε αυτές τις αλλαγές
Τώρα, πηγαίνετε στην καρτέλα Ιστορικό και ανοίξτε το αρχείο `Contributors.md` σε έναν επεξεργαστή κειμένου κάνοντας δεξί κλικ και επιλέγοντας "Ανοίγμα στον επεξεργαστή κειμένου". Κύλισε προς το τέλος της σελίδας και προσθέστε το όνομά σας, και στη συνέχεια αποθηκεύστε το αρχείο.
Παράδειγμα: Εάν το όνομά σας είναι Τάκης Παπαδόπουλος, θα πρέπει να φαίνεται ως εξής.
\[Τάκης Παπαδόπουλος](https://github.com/takis)
Βλέπετε ότι υπάρχουν αλλαγές στο Contributors.md και έχουν προστεθεί στο GitHub Desktop.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
Τώρα καταγράψτε αυτές τις αλλαγές:
Γράψτε το μήνυμα "Προσθήκη `<το-όνομά-σας>` στη λίστα των συντελεστών" στο πεδίο _περίληψη_.
Αντικαταστήστε `<το-όνομά-σας>` με το όνομά σας.
Κάντε κλικ στο κουμπί που λέει `Καταγραφή για προσθήκη-του-όνομά-σας`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
Στο κάτω μέρος, μπορείτε να δείτε ότι έχει δημιουργηθεί η καταγραφή.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit your changes" />
## Μεταφορά των αλλαγών στο GitHub
Κάντε κλικ στο Αρχείο->Επιλογές και συνδεθείτε στο Github.com. Πληκτρολογήστε το όνομα χρήστη και τον κωδικό πρόσβασής σας στο Github.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in to Github" />
Κάντε κλικ στο κουμπί `Δημοσίευση` στην πάνω δεξιά γωνία.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push your changes" />
## Υποβολή των αλλαγών σας για αξιολόγηση
Εάν μεταβείτε στο αποθετήριό σας στο GitHub, θα δείτε το κουμπί `Σύγκριση & αίτηση εξαγωγής` (Compare & pull request). Κάντε κλικ σε αυτό το κουμπί.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
Τώρα υποβάλετε το αίτημα εξαγωγής (pull request).
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
Σύντομα θα ενσωματώσω όλες τις αλλαγές σας στο κύριο κλαδί αυτού του έργου. Θα λάβετε ένα email ειδοποίησης όταν οι αλλαγές ενσωματωθούν.
## Πού να πάτε από εδώ;
Συγχαρητήρια! Μόλις ολοκληρώσατε την κανονική ροή _κλωνοποίηση -> κλωνοποίηση -> επεξεργασία -> αίτηση εξαγωγής_ που θα συναντήσετε συχνά ως συνεισφέροντας!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε τη με τους φίλους σας και τους ακόλουθούς σας μεταβαίνοντας στη [ιστοσελίδα εφαρμογής](https://firstcontributions.github.io#social-share).
Μπορείτε να εγγραφείτε στην ομάδα μας στο Slack αν χρειάζεστε βοήθεια ή έχετε ερωτήσεις. [Εγγραφείτε στην ομάδα Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Πρόσθετο υλικό](../additional-material/git_workflow_scenarios/additional-material.md)
## Οδηγοί Χρήσης Άλλων Εργαλείων
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Greek/github-windows-intellij-tutorial.gr.md
+110
View File
@@ -0,0 +1,110 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
| <img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/9/9c/IntelliJ_IDEA_Icon.svg" width="40"> | IntelliJ IDEA |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
Είναι δύσκολο. Είναι πάντα δύσκολο την πρώτη φορά που κάνετε κάτι. Ειδικά όταν συνεργάζεστε, οι λάθος δεν είναι κάτι άνετο. Αλλά το ανοιχτό κώδικα είναι όλο για συνεργασία και συνεργασία. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο νέοι συνεισφέροντες στον ανοιχτό κώδικα μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Το να διαβάζετε άρθρα και να παρακολουθείτε οδηγίες μπορεί να βοηθήσει, αλλά τι είναι καλύτερο από το να κάνετε πράγματα χωρίς να κάνετε κανένα λάθος. Αυτό το έργο στοχεύει στην παροχή καθοδήγησης και απλοποίησης του τρόπου που οι νεοσύστατοι συνεισφέροντες κάνουν την πρώτη τους συνεισφορά. Θυμηθείτε, όσο πιο χαλαροί είστε, τόσο καλύτερα μαθαίνετε. Εάν θέλετε να κάνετε την πρώτη σας συνεισφορά, απλά ακολουθήστε τα απλά βήματα παρακάτω. Σας υποσχόμαστε ότι θα είναι διασκεδαστικό.
Εάν δεν έχετε το IntelliJ IDEA στον υπολογιστή σας, [εγκαταστήστε το](https://www.jetbrains.com/idea/download/#section=windows).
**Σημείωση:** Αυτός ο οδηγός δημιουργήθηκε χρησιμοποιώντας το IntelliJ IDEA (Έκδοση 2019.3.2) σε μια μηχανή με λειτουργικό σύστημα Windows 10. Αργότερα σε αυτόν τον οδηγό θα χρησιμοποιήσουμε ορισμένες συντομεύσεις πληκτρολογίου. Αυτές μπορεί να διαφέρουν σε άλλα λειτουργικά συστήματα (macOS/Linux).
## Κλωνοποίηση αυτού του αποθετηρίου
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
Κλωνοποιήστε αυτό το αποθετήριο κάνοντας κλικ στο κουμπί "Fork" στην επάνω δεξιά γωνία αυτής της σελίδας. Αυτό θα δημιουργήσει αντίγραφο αυτού του αποθετηρίου στον λογαριασμό σας στο GitHub.
Το GitHub παρακολουθεί τη σχέση μεταξύ του αποθετηρίου σας και αυτού που το κλωνοποιήσατε. Μπορείτε να σκεφτείτε το αποθετήριο σας ως μια εργαστηριακή έκδοση.
Τα περισσότερα αποθετήρια GitHub στο επίπεδο της κορυφής (δηλαδή αυτά που δεν έχουν κλωνοποιηθεί από κανένα άλλο αποθετήριο) έχουν μια μικρή πυρήνα ομάδα ανθρώπων που μπορούν να διαπράξουν αλλαγές απευθείας. Όλοι οι άλλοι συνεισφέροντες πρέπει να κλωνοποιήσουν το αποθετήριο και να κάνουν αλλαγές στο κλωνοποιημένο αποθετήριο, και στη συνέχεια να δημιουργήσουν μια αίτηση εξαγωγής (Pull Request) για να ζητήσουν την ενσωμάτωση των αλλαγών τους στο αποθετήριο στο επίπεδο της κορυφής. Εάν ο διαχειριστής του αποθετηρίου στο επίπεδο της κορυφής εγκρίνει τις αλλαγές, θα ενσωματωθούν, και θα αποκτήσετε αμέσως φήμη και πλούτο! Περισσότερα για το πώς να το κάνετε αυτό αργότερα.
## Κλωνοποίηση του αποθετηρίου σας
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
Το επόμενο βήμα είναι να κλωνοποιήσετε το αποθετήριο σας στον υπολογιστή σας, ώστε να μπορείτε να αρχίσετε να κάνετε αλλαγές. Το IntelliJ IDEA χρειάζεται το URL του αποθετηρίου σας, οπότε κάντε κλικ στο κουμπί "Clone" και στη συνέχεια κάντε κλικ στο εικονίδιο "Copy to Clipboard".
**ΠΡΟΣΟΧΗ:** Ένα λάθος που συχνά κάνουν οι νέοι συνεισφέροντες είναι να κλωνοποιούν το αποθετήριο από το οποίο κλωνοποιήσατε αντί να κλωνοποιήσετε το δικό σας αποθετήριο. Ελέγξτε τη γραμμή διεύθυνσης του προγράμματος περιήγησής σας και βεβαιωθείτε ότι κάνετε κλωνοποίηση του δικού σας αποθετηρίου.
Ανοίξτε το IntelliJ IDEA.
Το IntelliJ IDEA σας επιτρέπει να κάνετε checkout (σε όρους Git κλωνοποίηση) ενός υπάρχοντος αποθετηρίου και να δημιουργήσετε ένα νέο έργο με βάση τα δεδομένα που έχετε λήψη.
Από το κύριο μενού, επιλέξτε VCS | Get from Version Control, ή, εάν δεν είναι ανοιχτό κάποιο έργο αυτή τη στιγμή, κάντε κλικ στο Get from Version Control στην οθόνη καλωσορίσματος.
Στο παράθυρο Get from Version Control, καθορίστε το URL του απομακρυσμένου αποθετηρίου που θέλετε να κλωνοποιήσετε (μπορείτε να κάνετε κλικ στο Test για να ελέγξετε εάν μπορεί να εδραιωθεί η σύνδεση με το απομακρυσμένο) ή επιλέξτε ένα από τις υπηρεσίες φιλοξενίας VCS στα αριστερά. Εάν έχετε ήδη συνδεθεί στην επιλεγμένη υπηρεσία φιλοξενίας, η συμπλήρωση θα προτείνει τη λίστα των διαθέσιμων αποθετηρίων που μπορείτε να κλωνοποιήσετε.
Κάντε κλικ στο Clone. Εάν θέλετε να δημιουργήσετε ένα έργο IntelliJ IDEA βασισμένο στις πηγές που έχετε κλωνοποιήσει, κάντε κλικ στο Yes στο παράθυρο επιβεβαίωσης. Η ρίζα του Git θα ρυθμιστεί αυτόματα στον κατάλογο ρίζας του έργου.
Εάν το έργο σας περιέχει υποέργα, θα κλωνοποιηθούν επίσης και θα εγγραφούν αυτόματα ως ρίζες έργου.
**Σημαντικό**: Βεβαιωθείτε ότι είναι το κλωνοποιημένο αποθετήριο και όχι το αρχικό, διαφορετικά δεν θα λειτουργήσει.
## Δημιουργία κλαδιού
Στο Git, η διακλάδωση είναι ένα ισχυρό μηχανισμό που σας επιτρέπει να αποκλίνετε από την κύρια γραμμή ανάπτυξης, για παράδειγμα, όταν χρειάζεστε να εργαστείτε σε μια λειτουργία ή να παγώσετε μια συγκεκριμένη κατάσταση ενός κώδικα για μια νέα έκδοση, κ.λπ.
Στο IntelliJ IDEA, όλες οι λειτουργίες με κλαδιά πραγματοποιούνται στην αναδυόμενη πλαίσιο "Git Branches". Για να το εκκινήσετε, κάντε κλικ στο εικονίδιο Git στη γραμμή κατάστασης ή πατήστε Ctrl+Shift+`.
Το όνομα του κλαδιού που είναι επί του παρόντος ελεγχόμενο εμφανίζεται στο widget Git στη γραμμή κατάστασης.
Στο αναδυόμενο πλαίσιο "Git Branches", επιλέξτε "New Branch" (Νέο Κλαδί).
Στο διάλογο που ανοίγει, καθορίστε το όνομα του κλαδιού και βεβαιωθείτε ότι η επιλογή "Checkout branch" (Επιλογή Κλαδιού) είναι επιλεγμένη εάν θέλετε να μεταβείτε σε αυτό το κλαδί.
Το νέο κλαδί θα ξεκινήσει από το τρέχον HEAD. Εάν θέλετε να ξεκινήσετε ένα κλαδί από μια προηγούμενη δέσμη αντί από το τρέχον HEAD του κλαδιού, επιλέξτε αυτήν τη δέσμη στον καρτέλα Καταγραφής του παραθύρου εργαλείων Έλεγχος Εκδόσεων Alt+9 και επιλέξτε "New Branch" από το μενού περιβάλλοντος.
## Κάντε τις απαραίτητες αλλαγές
Ανοίξτε το αρχείο `Contributors.md` και προσθέστε το όνομά σας οπουδήποτε στο αρχείο. Αυτό το αρχείο περιέχει GFM (GitHub Flavored Markdown), το οποίο είναι μια προπροπριεταρική γεύση της σύνταξης markdown.
Αντιγράψτε μία από τις γραμμές άλλων συνεισφερόντων και τροποποιήστε τη με το όνομά σας για να βεβαιωθείτε ότι έχετε σωστή σύνταξη - μπορεί να είναι απαιτητική.
## Κάντε Commit & Push τις αλλαγές στο GitHub
Επιλέξτε τα αρχεία που θέλετε να κάνετε commit ή ολόκληρη μια λίστα αλλαγών στο καρτέλα "Local Changes" του παραθύρου Εργαλείων Έλεγχος Εκδόσεων Alt+9 και πατήστε το Ctrl+K ή κάντε κλικ στο κουμπί "Commit" στη γραμμή εργαλείων.
Το παράθυρο "Commit Changes" που ανοίγει καταγράφει όλα τα αρχεία που έχουν τροποποιηθεί από την τελευταία δέσμη αλλαγών, καθώς και όλα τα νέα ανεκδότα αρχεία.
Εισάγετε ένα νόηματος commit μήνυμα.
Μπορείτε να κάνετε κλικ στην ιστορία των μηνυμάτων commit με την ιστορία των μηνυμάτων commit Ctrl+M για να επιλέξετε από τη λίστα των πρόσφατων μηνυμάτων commit.
Μπορείτε επίσης να επεξεργαστείτε το μήνυμα commit αργότερα πριν στείλετε το commit.
Πατήστε το Ctrl+Shift+K ή επιλέξτε VCS | Git | Push από το κύριο μενού. Το παράθυρο "Push Commits" ανοίγει και εμφανίζει όλα τα αποθετήρια Git (για πολυ-αποθετήρια έργα) και καταγράφει όλες τις δεσμές αλλαγών που έχουν γίνει στο τρέχον κλαδί σε κάθε αποθετήριο από την τελευταία αποστολή.
## Υποβάλλετε τις αλλαγές σας για αξιολόγηση
Σε αυτό το σημείο, έχετε ολοκληρώσει την αλλαγή σας, αλλά αυτή βρίσκεται ακόμα μόνο στο αποθετήριό σας. Αυτό το βήμα θα σας δείξει πώς να υποβάλετε αίτηση στον διαχειριστή του αποθετηρίου στο επίπεδο της κορυφής για να ενσωματώσετε την αλλαγή σας.
Στο αποθετήριό σας στο GitHub, θα δείτε το κουμπί "Compare & pull request" (Σύγκριση & αίτηση εξαγωγής) δίπλα στην ειδοποίηση για το νέο κλαδί. Κάντε κλικ σε αυτό το κουμπί.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
Στη συνέχεια, υποβάλετε την αίτηση εξαγωγής (Pull Request).
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
Σύντομα, θα συγχωνεύσω όλες τις αλλαγές σας στο κύριο κλαδί αυτού του έργου. Θα λάβετε ένα email ειδοποίησης μόλις οι αλλαγές σας έχουν συγχωνευτεί.
## Πού να πάτε από εδώ και πέρα;
Συγχαρητήρια! Μόλις ολοκληρώσατε την κανονική ροή _fork -> clone -> edit -> PR_ που θα συναντήσετε συχνά ως συνεισφέροντας!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε τη με τους φίλους και τους ακόλουθούς σας μεταβαίνοντας στην [ιστοσελίδα της εφαρμογής](https://firstcontributions.github.io#social-share).
Μπορείτε να ενταχθείτε στην ομάδα μας στο Slack σε περίπτωση που χρειάζεστε βοήθεια ή έχετε ερωτήσεις. [Ενταχθείτε στην ομάδα Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Πρόσθετο υλικό](../additional-material/git_workflow_scenarios/additional-material.md)
## Οδηγοί για Χρήση Άλλων Εργαλείων
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Greek/github-windows-vs-code-tutorial.gr.md
+115
View File
@@ -0,0 +1,115 @@
[![Αγάπη για το Ανοιχτό Κώδικα](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Άδεια: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Βοηθοί Ανοιχτού Κώδικα](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
Είναι δύσκολο. Είναι πάντα δύσκολο την πρώτη φορά που κάνετε κάτι. Ειδικά όταν συνεργάζεστε, το να κάνετε λάθη δεν είναι κάτι άνετο. Αλλά το ανοιχτός κώδικας αφορά τη συνεργασία και την εργασία μαζί. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο νέοι συνεισφέροντες ανοιχτού κώδικα μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Το να διαβάζετε άρθρα και να παρακολουθείτε μαθήματα μπορεί να βοηθήσει, αλλά τι καλύτερο από το να κάνετε πράγματα χωρίς να μπερδευτείτε με τίποτα. Αυτό το έργο στοχεύει στην παροχή καθοδήγησης και στην απλοποίηση του τρόπου που οι νεοσύστατοι συνεισφέροντες κάνουν την πρώτη τους συνεισφορά. Θυμηθείτε ότι όσο πιο χαλαροί είστε, τόσο καλύτερα μαθαίνετε. Εάν ψάχνετε να κάνετε την πρώτη σας συνεισφορά, απλώς ακολουθήστε τα απλά βήματα παρακάτω. Σας υποσχόμαστε, θα είναι διασκεδαστικό.
Εάν δεν έχετε το Visual Studio Code στον υπολογιστή σας, [εγκαταστήστε το](https://code.visualstudio.com/download).
**Προσοχή:** Αυτός ο οδηγός δημιουργήθηκε χρησιμοποιώντας το Visual Studio Code (Έκδοση 1.27.2) σε μηχάνημα με Windows 10. Αργότερα σε αυτόν τον οδηγό, θα χρησιμοποιήσουμε κάποιες συντομεύσεις πληκτρολογίου. Αυτές μπορεί να διαφέρουν σε άλλα λειτουργικά συστήματα (macOS/Linux) καθώς και σε γλώσσες πληκτρολογίου (UK, DE, κλπ). Μπορείτε να εξετάσετε τη λίστα των συντομεύσεων σας αναζητώντας "συντόμευση" στην Εντολική Παλέτα (Command Palette).
## Κάντε Fork το αποθετήριο
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Κάντε fork το αποθετήριο κάνοντας κλικ στο κουμπί fork στην πάνω δεξιά γωνία αυτής της σελίδας. Αυτό θα δημιουργήσει ένα αντίγραφο αυτού του αποθετηρίου στο λογαριασμό σας στο GitHub.
Το GitHub κρατάει το ιστορικό της σχέσης μεταξύ του αποθετηρίου σας και του αποθετηρίου από το οποίο το κάνατε fork. Μπορείτε να φανταστείτε το αποθετήριο σας ως μια εργασιακή αντιγραφή.
Τα περισσότερα ανώτατα αποθετήρια του GitHub (δηλαδή αυτά που δεν έχουν γίνει fork από κάποιο άλλο αποθετήριο) έχουν μια μικρή ομάδα πυρήνα ανθρώπων που μπορούν να κάνουν απευθείας αλλαγές. Όλοι οι άλλοι συνεισφέροντες πρέπει να κάνουν fork το αποθετήριο και να κάνουν αλλαγές στο fork, στη συνέχεια να δημιουργήσουν ένα αίτημα εξαγωγής (Pull Request) για να ζητήσουν τις αλλαγές τους να συγχωνευτούν πίσω στο ανώτατο αποθετήριο. Εάν ο διαχειριστής του ανώτατου αποθετηρίου αρέσει τις αλλαγές, θα συγχωνευτούν και θα κερδίσετε αμέσως φήμη και πλούτο! Περισσότερα γι' αυτό αργότερα.
## Κλωνοποίηση του αποθετηρίου σας
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
Το επόμενο βήμα είναι να κλωνοποιήσετε το αποθετήριο στον υπολογιστή σας, ώστε να μπορείτε να αρχίσετε να κάνετε αλλαγές. Το VS Code χρειάζεται τη διεύθυνση URL του αποθετηρίου σας, οπότε κάντε κλικ στο κουμπί "code" και στη συνέχεια κάντε κλικ στο εικονίδιο "copy to clipboard".
**ΠΡΟΣΟΧΗ:** Ένα λάθος που κάνουν συχνά οι νέοι συνεισφέροντες είναι να κλωνοποιούν το αποθετήριο από το οποίο έκαναν fork _αντί να κλωνοποιούν το δικό τους αποθετήριο_. Ελέγξτε τη γραμμή διεύθυνσης του προγράμματος περιήγησής σας και βεβαιωθείτε ότι κάνετε κλωνοποίηση του δικού σας αποθετηρίου.
Τώρα ανοίξτε το Visual Studio Code. Η αρχική σελίδα του VS Code θα εμφανιστεί. Από εκεί πατήστε `F1` για να ανοίξετε τη γραμμή εργαλείων που εμφανίζεται παρακάτω. Παρατηρήστε ότι υπάρχει ήδη ένα `>` (μεγαλύτερο από) στο πεδίο κειμένου. Μπορείτε επίσης να φτάσετε στο προσαρτημένο παράθυρο εισαγωγής πατώντας `CTRL-P` και στη συνέχεια πληκτρολογώντας τον χαρακτήρα `>`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Μπορεί να παρατηρήσετε ότι υπάρχουν ήδη κάποιες ασαφείς εντολές που εμφανίζονται παρακάτω. Αυτές είναι οι πρόσφατα χρησιμοποιημένες εντολές μου. Απλώς μην ασχολείστε μαζί τους.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Τώρα πληκτρολογήστε `git clone`, μόνο `git` ή `clone` (λειτουργεί σαν αναζήτηση). Επιλέξτε την εισαγωγή `Git: Clone` και πατήστε `Enter`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
Επικολλήστε τη διεύθυνση URL του αποθετηρίου σας και πατήστε `Enter`. Αυτό θα ανοίξει ένα Εξερευνητή Αρχείων όπου μπορείτε στη συνέχεια να επιλέξετε πού θα αποθηκευτεί το αποθετήριο Git.
**Σημαντικό**: Βεβαιωθείτε ότι είναι το αποθετήριο fork και όχι το αρχικό, διαφορετικά δεν θα λειτουργήσει.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Θα δείτε ένα αναδυόμενο παράθυρο κατάστασης στο κάτω δεξιό μέρος του Visual Studio Code. Αφού ολοκληρωθεί, μπορείτε να ανοίξετε το κλωνοποιημένο αποθετήριο (που τώρα είναι ένας φάκελος στον υπολογιστή σας) χρησιμοποιώντας τα κουμπιά στο διάλογο.
## Δημιουργία ενός κλαδιού
Άνοιξτε ξανά τη γραμμή εργαλείων πληκτρολογώντας `F1`. Πληκτρολογήστε `branch` και επιλέξτε την εντολή `create branch`. Στο επόμενο βήμα, πληκτρολογήστε το όνομα του νέου σας κλαδιού, για παράδειγμα `add-david-kroell`. Πατήστε Enter και το κλαδί θα δημιουργηθεί. Το κλαδί είναι επίσης ήδη ελεγχθεί. [Τι σημαίνει η εντολή checkout;](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Κάντε τις απαραίτητες αλλαγές
Ανοίξτε το αρχείο `Contributors.md` και προσθέστε το όνομά σας οπουδήποτε στο αρχείο. Αυτό το αρχείο περιέχει GFM (GitHub Flavored Markdown), που είναι μια προσαρμοσμένη έκδοση της σύνταξης <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Αντιγράψτε μία από τις γραμμές άλλων συνεισφερόντων και τροποποιήστε τη με το όνομά σας για να βεβαιωθείτε ότι καταλαβαίνετε τη σύνταξη - μπορεί να είναι απαιτητική. Αποθηκεύστε το αρχείο για να καταγραφεί η αλλαγή.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Κάντε Commit & Push τις αλλαγές στο GitHub
Στο αριστερό μέρος του VS Code υπάρχει ένα μενού με 5 εικονίδια. Επιλέξτε το εικονίδιο έλεγχου εκδόσεων/Ελέγχου Κώδικα.
(Συντόμευση: Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
Ο εξερευνητής αρχείων εμφανίζει όλα τα αρχεία που έχουν αλλάξει μετά το τελευταίο commit. Αν φέρετε το ποντίκι πάνω από τα αρχεία και κάνετε κλικ στο `+` (συν ή πλήκτρο plus), τα αρχεία είναι σταγμένα (staged).
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
Πληκτρολογήστε κάτι στη γραμμή στην κορυφή του εξερευνητή και πατήστε το σημάδι επιλογής ελέγχου. Οι αλλαγές καταγράφονται τώρα στο τοπικό αντίγραφό σας. Τώρα οι αλλαγές πρέπει να ανέβουν πίσω στο GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
Χρησιμοποιήστε το εικονίδιο με τις τρεις τελείες για να ανοίξετε το μενού όπου θα επιλέξετε την επιλογή `Publish Branch` (Δημοσίευση Κλαδιού). Αυτό πρέπει να ανοίξει ένα παράθυρο διαλόγου για να εισαγάγετε τα διαπιστευτήρια σας στο GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## Υποβάλετε τις αλλαγές σας για αξιολόγηση
Σε αυτό το σημείο, έχετε ολοκληρώσει την αλλαγή σας αλλά αυτή βρίσκεται ακόμα μόνο στο αποθετήριό σας. Αυτό το βήμα θα σας δείξει πώς να υποβάλετε ένα αίτημα στο διαχειριστή του ανώτατου αποθετηρίου για να συγχωνευτεί η αλλαγή σας.
Στο αποθετήριό σας στο GitHub, θα δείτε το κουμπί "Compare & pull request" (Σύγκριση & αίτημα εξαγωγής) δίπλα στην ειδοποίηση για το νέο κλαδί. Κάντε κλικ σε αυτό το κουμπί.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Υποβάλετε το αίτημα εξαγωγής (pull request).
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Σύντομα θα συγχωνευτούν όλες οι αλλαγές σας στο κύριο κλαδί αυτού του έργου. Θα λάβετε ένα email ειδοποίησης μόλις οι αλλαγές σας συγχωνευτούν.
## Πού να πάτε από εδώ;
Συγχαρητήρια! Μόλις ολοκληρώσατε την τυπική ροή _fork -> clone -> edit -> PR_ που θα συναντήσετε συχνά ως συνεισφέροντας!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε την με τους φίλους και τους ακόλουθούς σας πηγαίνοντας στη [web εφαρμογή](https://firstcontributions.github.io#social-share).
Μπορείτε να εγγραφείτε στην ομάδα μας στο Slack αν χρειάζεστε βοήθεια ή έχετε ερωτήσεις. [Εγγραφή στην ομάδα Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Επιπλέον υλικό](../additional-material/git_workflow_scenarios/additional-material.md)
## Οδηγοί χρήσης με άλλα εργαλεία
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Greek/github-windows-vs2017-tutorial.gr.md
+145
View File
@@ -0,0 +1,145 @@
[![Αγάπη για το Ανοιχτό Κώδικα](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Άδεια: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Βοηθοί Ανοιχτού Κώδικα](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
|<img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/61/Visual_Studio_2017_logo_and_wordmark.svg/2000px-Visual_Studio_2017_logo_and_wordmark.svg.png" width="200">|Έκδοση Visual Studio 2017|
|---|---|
Είναι δύσκολο. Πάντα είναι δύσκολο την πρώτη φορά που κάνεις κάτι. Ειδικά όταν συνεργάζεσαι, οι λάθος δεν είναι κάτι άνετο. Αλλά ο ανοιχτός κώδικας αφορά τη συνεργασία και την εργασία μαζί. Ήθελαν να απλοποιήσουν τον τρόπο με τον οποίο νέοι συνεισφέροντες ανοιχτού κώδικα μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Το να διαβάζεις άρθρα και να παρακολουθείς οδηγούς μπορεί να βοηθήσει, αλλά τίποτα δεν είναι καλύτερο από το να κάνεις πραγματικά τα πράγματα χωρίς να χαλάσεις τίποτα. Αυτό το έργο στοχεύει να παρέχει καθοδήγηση και να απλοποιεί τον τρόπο που οι νέοι συνεισφέροντες κάνουν την πρώτη τους συνεισφορά. Θυμήσου, όσο πιο χαλαρός είσαι, τόσο καλύτερα μαθαίνεις. Αν ψάχνεις να κάνεις την πρώτη σου συνεισφορά, ακολούθησε απλά τα απλά βήματα παρακάτω. Σου υποσχόμαστε, θα είναι διασκεδαστικό.
Αν δεν έχετε την Visual Studio 2017 στη μηχανή σας, [εγκαταστήστε την](https://www.visualstudio.com/downloads/).
## Κλωνοποίηση του αποθετηρίου
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/fork.png" alt="κλωνοποίηση του αποθετηρίου" />
Κλωνοποιήστε αυτό το αποθετήριο κάνοντας κλικ στο κουμπί "fork" στην κορυφή αυτής της σελίδας. Αυτό θα δημιουργήσει ένα αντίγραφο αυτού του αποθετηρίου στο λογαριασμό σας στο GitHub.
Το GitHub παρακολουθεί τη σχέση ανάμεσα στο αποθετήριό σας και αυτό από το οποίο το διακλαδώσατε. Μπορείτε να σκεφτείτε το αποθετήριό σας ως μια εργασιακή αντιγραφή.
Τα περισσότερα αποθετήρια GitHub επιπέδου κορυφής (δηλαδή εκείνα που δεν διακλαδώθηκαν από κανένα άλλο αποθετήριο) έχουν μια μικρή πυρήνα ομάδα ανθρώπων που μπορούν να κάνουν απευθείας αλλαγές. Οι υπόλοιποι συνεισφέροντες πρέπει να διακλαδώσουν το αποθετήριο και να κάνουν αλλαγές στο διακλάδωμα, και στη συνέχεια να δημιουργήσουν ένα αίτημα τραβήγματος για να ζητήσουν τις αλλαγές τους να ενσωματωθούν πίσω στο αποθετήριο επιπέδου κορυφής. Εάν ο διαχειριστής του αποθετηρίου επιπέδου κορυφής αρέσει τις αλλαγές, θα ενσωματώνονται και θα κερδίσετε άμεση φήμη και πλούτο! Περισσότερα για το πώς να το κάνετε αυτό αργότερα.
## Κλωνοποίηση του αποθετηρίου σας
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/clone.png" alt="κλωνοποίηση αυτού του αποθετηρίου" />
Ο επόμενος βήμα είναι να κλωνοποιήσετε το αποθετήριο σας στη μηχανή σας ώστε να μπορέσετε να αρχίσετε να κάνετε αλλαγές. Η Visual Studio χρειάζεται το URL του αποθετηρίου σας, οπότε κάντε κλικ στο κουμπί "clone" και στη συνέχεια κάντε κλικ στο εικονίδιο "αντιγραφή στο πρόχειρο".
**ΠΡΟΣΟΧΗ:** Ένα σφάλμα που κάνουν συχνά οι νέοι συνεισφέροντες είναι να κλωνοποιούν το αποθετήριο που διακλάδωσαν *από* αντί να κλωνοποιούν το αποθετήριο τους. Ελέγξτε τη γραμμή διεύθυνσης του προγράμματος περιήγησής σας και βεβαιωθείτε ότι κλωνοποιείτε το αποθετήριό σας.
Τώρα είναι η στιγμή να μεταβείτε στην Visual Studio 2017! Θα εργαστείτε στην καρτέλα "Ομάδα Εξερεύνησης" για το μεγαλύτερο μέρος αυτού του οδηγού. Εάν δεν είναι ανοικτή από προεπιλογή, κάντε κλικ στο `Προβολή > Ομάδα Εξερεύνησης` για να την ανοίξετε.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-01-clone1.png" alt="Ομάδα Εξερεύνησης" />
Η Ομάδα Εξερεύνησης έχει πολλές προβολές και υπάρχουν κουμπιά πλοήγησης στην κορυφή για να σας βοηθήσουν να βρείτε τις διάφορες περιοχές. Για να κλωνοποιήσετε ένα αποθετήριο, πρέπει να βρίσκεστε στην προβολή Σύνδεση, η οποία πρέπει να είναι η προεπιλεγμένη. Εάν δεν βλέπετε το κουμπί "κλώνος", κάντε κλικ στην πράσινη πρίζα στην κορυφή.
Κάντε κλικ στην επιλογή "Κλώνος" κάτω από **Τοπικά Αποθετήρια Git** και επικολλήστε το URL του αποθετηρίου σας στο πλαίσιο κειμένου. Αυτό θα πρέπει να είναι το URL που έχετε αντιγράψει στο πρόχειρο από το GitHub προηγουμένως.
Κάντε κλικ στο κουμπί "Κλώνος" για να ξεκινήσετε τη διαδικασία.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-02-clone2.png" alt="Κλώνος αποθετηρίου" />
Όταν ολοκληρωθεί η διαδικασία, θα μεταφερθείτε στην καρτέλα Εξερεύνησης Λύσης, όπου μπορείτε να δείτε τα περιεχόμενα του αποθετηρίου σας. Το δικό σας θα διαφέρει από τη στιγμιότυπη λήψη παρακάτω επειδή τα πράγματα αλλάζουν!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-03-clone3.png" alt="Εξερεύνηση Λύσης" />
## Δημιουργία κλαδιού
Κάντε κλικ πίσω στην καρτέλα Ομάδα Εξερεύνησης και χρησιμοποιήστε το κυρίως αναπτυσσόμενο μενού πλοήγησης για να ανοίξετε την προβολή Κλαδιά.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-04-branch1.png" alt="Προβολή Κλαδιών" />
Θα πρέπει να δείτε το αποθετήριο **first-contributions** και το προεπιλεγμένο κλαδί, το οποίο ονομάζεται `master`. Κάντε δεξί κλικ στο `master` και επιλέξτε "Δημιουργία Νέου Τοπικού Κλαδιού Από...".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-05-branch2.png" alt="Νέο κλαδί" />
Δώστε στο κλαδί σας ένα όνομα όπως `add-<όνομα_σας_εδώ>`, για παράδειγμα: `add-alonzo-church`.
Αφήστε το πλαίσιο "Έλεγχος κλαδιού" επιλεγμένο και κάντε κλικ στο κουμπί "Δημιουργία Κλαδιού".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-06-branch3.png" alt="Δημιουργία κλαδιού" />
Θα πρέπει να δείτε το νέο κλαδί σας στη λίστα.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-07-branch4.png" alt="Προβολή νέου κλαδιού" />
Here is the translation of the remaining text:
## Κάντε τις απαραίτητες αλλαγές
Ανοίξτε το αρχείο `Contributors.md` και προσθέστε το όνομά σας στο τέλος της λίστας. Αυτό το αρχείο περιέχει την GFM (GitHub Flavored Markdown), η οποία είναι μια προπριεταριακή παραλλαγή της [σύνταξης Markdown](https://en.wikipedia.org/wiki/Markdown).
Αντιγράψτε μία από τις γραμμές άλλων συνεισφερόντων και τροποποιήστε τη με το όνομά σας για να βεβαιωθείτε ότι έχετε σωστή σύνταξη - μπορεί να είναι λεπτομερής.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-08-change1.png" alt="Προσθήκη του ονόματός σας" />
## Κάντε commit & αποστείλετε τις αλλαγές στο GitHub
Μεταβείτε πίσω στο Team Explorer και πλοηγηθείτε στην προβολή Αλλαγές.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-09-commit1.png" alt="Αλλαγές" />
Εισαγάγετε τις πληροφορίες που θέλετε να προσθέσετε με το commit σας και κάντε κλικ στο "Αποθήκευση". Το Visual Studio θα το θυμάται για μελλοντικά commit.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-10-commit2.png" alt="Πληροφορίες χρήστη Git" />
**ΣΗΜΕΙΩΣΗ:** Το Visual Studio χρησιμοποιεί έναν κρυφό φάκελο με το όνομα `.vs` για να αποθηκεύει τις προσωπικές σας ρυθμίσεις και προτιμήσεις. Τα περιεχόμενα αυτού του φακέλου **δεν πρέπει να αποθηκευτούν στο Git**. Αν δεν έχει ήδη γίνει αγνόησή του, μπορεί να χρειαστεί να ενημερώσετε το Git να τον αγνοεί, ώστε να μην τον αποστέλλει στο αποθετήριο.
Αυτός ο φάκελος έχει ήδη αγνοηθεί σε αυτό το αποθετήριο, οπότε δεν θα χρειαστεί να εκτελέσετε αυτό το βήμα... είναι απλά εδώ για την αναφορά σας για μελλοντικά έργα.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-11-commit3.png" alt="Παράβλεψη του φακέλου .vs" />
Τώρα θα πρέπει να δείτε μια λίστα με τα αλλαγμένα αρχεία και ένα πλαίσιο κειμένου για να πληκτρολογήσετε ένα σχόλιο commit. Τα σχόλια πρέπει να είναι σύντομα, αλλά λεπτομερή. Δεν υπάρχει χειρότερο από το να διαβάζετε σχόλια commit και να βλέπετε κάτι τέτοιο: `"Έκανα ανανεώσεις"`. Αφιερώστε λίγα δευτερόλεπτα για να περιγράψετε το commit σας. Η ομάδα σας θα σας ευγνωμονήσει αργότερα, και εσ
είς μπορείτε ακόμα και να ευχαριστήσετε τον εαυτό σας!
Κάντε κλικ στο "Καταχώρηση όλων και αποστολή" για να πραγματοποιήσετε ένα τοπικό commit και να αποστείλετε τις αλλαγές σας πίσω στο αποθετήριό σας, όλα με ένα βήμα.
**ΣΗΜΕΙΩΣΗ:** Το commit μπορεί να γίνει ξεχωριστά από το Push. Εδώ κάνουμε και τα δύο για άνεση. Το commit καταγράφει τις αλλαγές σας τοπικά, αλλά δεν θα αντανακλαστούν στο αποθετήριό σας στο GitHub μέχρι να κάνετε Push.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-12-commit4.png" alt="Καταχώρηση και αποστολή" />
Την πρώτη φορά που θα κάνετε Push στο GitHub, το Visual Studio θα ζητήσει τα διαπιστευτήριά σας στο GitHub. Θα αποθηκευτούν στη μνήμη cache, οπότε δεν θα βλέπετε αυτό πολύ συχνά.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-13-commit5.png" alt="Σύνδεση" />
Αφού ολοκληρωθεί η λειτουργία Push, ανοίξτε το αποθετήριό σας στο GitHub και θα δείτε ένα μήνυμα που υποδεικνύει μια πρόσφατα απεσταλμένη κλαδί.
Μπορείτε να δείτε τις αλλαγές σας ανοίγοντας το αναπτυσσόμενο μενού "Branch: master" και επιλέγοντας το νέο σας κλαδί. Συγχαρητήρια, μπορείτε να μοιραστείτε το URL του κλαδιού με τον κόσμο για να δείξετε την πρόοδό σας!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-14-commit6.png" alt="Προβολή απεσταλμένου κλαδιού στο GitHub" />
## Υποβάλλετε τις αλλαγές σας για αναθεώρηση
Σε αυτό το σημείο, έχετε ολοκληρώσει την αλλαγή σας, αλλά εξακολουθεί να βρίσκεται μόνο στο αποθετήριό σας. Αυτό το βήμα θα σας δείξει πώς να υποβάλετε αίτημα προς τον διαχειριστή του ανώτατου επιπέδου αποθετηρίου για να ενσωματώσετε την αλλαγή σας.
Στο αποθετήριό σας στο GitHub, θα δείτε το κουμπί "Σύγκριση & αίτηση ενσωμάτωσης" δίπλα στην ειδοποίηση του νέου κλαδιού. Κάντε κλικ σε αυτό το κουμπί.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/compare-and-pull.png" alt="Δημιουργία αίτησης ενσωμάτωσης" />
Τώρα υποβάλετε το αίτημα ενσωμάτωσης.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/submit-pull-request.png" alt="Υποβολή αίτησης ενσωμάτωσης" />
Σύντομα θα συνοψίσω όλες τις αλλαγές σας στον κ
ύριο κλαδί αυτού του έργου. Θα λάβετε ένα email ειδοποίησης όταν οι αλλαγές έχουν ενσωματωθεί.
## Τι να κάνετε μετά;
Συγχαρητήρια! Έχετε μόλις ολοκληρώσει την κανονική ροή εργασίας "fork -> clone -> edit -> PR" που θα συναντήσετε συχνά ως συνεισφέροντας!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε τη με τους φίλους και τους ακόλουθούς σας πηγαίνοντας στην [ιστοσελίδα εφαρμογής](https://firstcontributions.github.io#social-share).
Μπορείτε να εγγραφείτε στην ομάδα μας στο Slack αν χρειαστείτε βοήθεια ή έχετε οποιεσδήποτε ερωτήσεις. [Εγγραφή στην ομάδα Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Πρόσθετο υλικό](../additional-material/git_workflow_scenarios/additional-material.md)
## Οδηγοί χρήσης άλλων εργαλείων
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Greek/gitkraken-tutorial.gr.md
+107
View File
@@ -0,0 +1,107 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
|<img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="200">|Έκδοση GitKraken|
|---|---|
Είναι δύσκολο. Είναι πάντα δύσκολο, όταν κάνετε κάτι για πρώτη φορά. Ειδικά όταν συνεργάζεστε, το να κάνεις κάποιο λάθος δεν είναι κάτι άνετο. Αλλά ο ανοιχτός κώδικας αφορά τη συνεργασία και τη συνεργασία. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο νέοι συνεισφέροντες ανοιχτού κώδικα μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Η ανάγνωση άρθρων και η παρακολούθηση εκπαιδευτικού υλικού μπορεί να βοηθήσει, αλλά τι είναι καλύτερο από το να κάνετε όντως κάτι χωρίς να χαλάσετε τίποτα. Αυτό το έργο έχει σκοπό να παρέχει καθοδήγηση και να απλοποίησει τον τρόπο με τον οποίο οι νέοι συνεισφέροντες μπορούν να κάνουν την πρώτη τους συνεισφορά. Θυμηθείτε, όσο πιο χαλαροί είστε, τόσο καλύτερα μαθαίνετε. Εάν θέλετε να κάνετε την πρώτη σας συνεισφορά, ακολουθήστε απλά τα απλά βήματα παρακάτω. Σας υποσχόμαστε, θα είναι διασκεδαστικό.
## GitKraken
Κατεβάστε το [GitKraken](https://www.gitkraken.com), εγκαταστήστε το και ανοίξτε το.
Θα δείτε το παράθυρο "Καλώς ήρθατε στο GitKraken" - Συνδεθείτε με το GitHub και επιτρέψτε στο GitKraken να αποκτήσει πρόσβαση στον λογαριασμό σας στο GitHub.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(προαιρετικά) Πηγαίνετε στο Αρχείο -> Προτιμήσεις και ορίστε τον κατάλογο του έργου σας στη ρίζα των τοπικών αποθετηρίων σας.
## Κάντε Fork αυτού του αποθετηρίου
Κάντε fork αυτό το αποθετήριο κάνοντας κλικ στο κουμπί fork στην κορυφή αυτής της σελίδας.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="fork this repository" />
Αυτό θα δημιουργήσει ένα αντίγραφο αυτού του αποθετηρίου στο λογαριασμό σας.
## Κλωνοποίηση του αποθετηρίου
Στο GitKraken, πηγαίνετε στο Αρχείο -> Κλωνοποίηση Αποθετηρίου.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
Επιλέξτε το GitHub.com στο δεξί πλαίσιο. Κάτω από το όνομα χρήστη σας, θα πρέπει να δείτε το first-contributions. Κάντε κλικ σε αυτό το αποθετήριο και ελέγξτε την πλήρη διαδρομή που εμφανίζεται στο κάτω μέρος αυτού του παραθύρου.
Μόλις είστε ικανοποιημένοι με τη διαδρομή, κάντε κλικ στο "Κλωνοποίηση του αποθετηρίου!".
## Δημιουργία παρακλαδιού
Κάντε κλικ στο κουμπί παρακλαδιού στη γραμμή εργαλείων.
Ονομάστε το παρακλάδι σας "προσθήκη-του-ονόματός-σας", για παράδειγμα: "προσθήκη-ονόματος-William-Sutton"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## Κάντε τις απαραίτητες αλλαγές και δεσμεύστε αυτές τις αλλαγές
Ανοίξτε τώρα το αρχείο `Contributors.md` σε έναν επεξεργαστή κειμένου και προσθέστε το όνομά σας σε αυτό, και στη συνέχεια αποθηκεύστε το αρχείο.
Εάν έχετε το αποθετήριο ανοικτό στο GitKraken, θα δείτε ότι υπάρχουν αλλαγές. Ελέγξτε και κάντε stage αυτές τις αλλαγές επιλέγοντας την νεότερη δέσμευση που είναι σημειωμένη με "// WIP" και τον αριθμό των αρχείων που έχουν αλλάξει και τον τύπο της αλλαγής.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
Επανεξετάστε τα αρχεία που έχουν αλλάξει και αποφασίστε τι θέλετε να τα κάνετε stage. Το staging είναι σημαντικό για να πείτε στο Git ακριβώς ποιες αλλαγές αρχείων θέλετε να συσχετίσετε με αυτήν τη δέσμευση.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
Αφού έχετε ένα καλό μήνυμα δεσμεύσεως ("Προσθήκη <του-ονόματός-σας> στη λίστα συνεισφερόντων" ακούγεται ωραίο και περιγραφικό) και είστε ικανοποιημένοι με τις αλλαγές σας, μπορείτε να πατήσετε "Stage όλων των αλλαγών" για να κάνετε stage όλα όσα έχουν τροποποιηθεί ή "Stage αρχείου" για να κάνετε stage ένα μεμονωμένο αρχείο.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
Εάν αλλάξετε γνώμη, μπορείτε να ακυρώσετε το staging αυτών των αλλαγών ή να τις απορρίψετε εντελώς.
ΠΡΟΕΙΔΟΠΟΙΗΣΗ: Όπως υποδηλώνει η λέξη απόρριψη, αυτή είναι μια καταστροφική λειτουργία. Κάντε αυτό μόνο εάν δεν θέλετε καμία αλλαγή από το αποθετήριο στο οποίο βρίσκεστε.
Πατήστε δέσμευση.
Συγχαρητήρια, έχετε δεσμεύσει όλες τις αλλαγές στο τοπικό αντίγραφο του κλαδιού σας του δικού σας fork του first-contributions. Συνεχίζουμε!
## Ανέβασμα αλλαγών στο GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
Πατήστε το κουμπί Ανέβασμα στη γραμμή εργαλείων.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
Υποβάλετε αλλαγές στο παρακλάδι origin εάν θέλετε οι αλλαγές να αντανακλούν απευθείας στον παρακλάδι master, διαφορετικά επιλέξτε το κατάλληλο παρακλάδι που θέλετε να ανεβάσετε.
## Υποβολή των αλλαγών σας για αξιολόγηση
Εάν πάτε στο αποθετήριο σας στο github, θα δείτε το κουμπί "Σύγκριση & αίτηση εξαγωγής". Κάντε κλικ σε αυτό το κουμπί.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
Τώρα υποβάλετε το αίτημα εξαγωγής.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit pull request" />
Σύντομα θα ενσωματώσω όλες τις αλλαγές σας στον κύριο παρακλάδι αυτού του έργου. Θα λάβετε μια ειδοποίηση με ηλεκτρονικό ταχυδρομείο αφού οι αλλαγές έχουν ενσωματωθεί.
## Πού να πάτε από εδώ;
Συγχαρητήρια! Μόλις ολοκληρώσατε την τυπική ροή _fork -> clone -> edit -> PR_ που θα συναντήσετε συχνά ως συνεισφέρων!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε την με τους φίλους σας και τους ακόλουθούς σας πηγαίνοντας στην [ιστοσελίδα του διαδικτυακού εργαλείου](https://firstcontributions.github.io/#social-share).
Μπορείτε να εγγραφείτε στην ομάδα μας στο slack εάν χρειάζεστε βοήθεια ή έχετε οποιεσδήποτε ερωτήσεις. [Εγγραφή στην ομάδα slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Πρόσθετο υλικό](../additional-material/git_workflow_scenarios/additional-material.md)
## Οδηγοί Χρήσης Άλλων Εργαλείων
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Greek/sourcetree-macos-tutorial.gr.md
+133
View File
@@ -0,0 +1,133 @@
[![Αγάπη Ανοικτού Κώδικα](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Άδεια: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Βοηθοί Ανοικτού Κώδικα](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
|<img alt="SourceTree" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-logo.png" width="200">|Atlassian Sourcetree|
|---|---|
Είναι δύσκολο. Είναι πάντα δύσκολο, όταν κάνεις κάτι για πρώτη φορά. Ειδικά όταν συνεργάζεσαι, το να κάνεις λάθη δεν είναι άνετο. Αλλά το ανοικτός κώδικας αφορά τη συνεργασία και την αλληλεπίδραση. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο νέοι συνεισφέροντες στον ανοικτό κώδικα μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Το να διαβάζεις άρθρα και να παρακολουθείς μαθήματα μπορεί να βοηθήσει, αλλά τι μπορεί να είναι καλύτερο από το να κάνεις πραγματικά τα πράγματα χωρίς να μπλέκεις τίποτα. Αυτό το πρόγραμμα στοχεύει στην παροχή καθοδήγησης και στην απλοποίηση του τρόπου με τον οποίο οι νέοι κάνουν την πρώτη τους συνεισφορά. Θυμήσου ότι όσο πιο χαλαρός είσαι, τόσο καλύτερα μαθαίνεις. Αν ψάχνεις να κάνεις την πρώτη σου συνεισφορά, ακολούθησε τα απλά βήματα παρακάτω. Σου υποσχόμαστε ότι θα είναι διασκεδαστικό.
## Sourcetree
Παρακαλούμε σημειώστε ότι αυτό το εκπαιδευτικό εγχειρίδιο αφορά το MacOS. Είναι παρόμοιο με το Sourcetree στα Windows, αλλά κάποια πράγματα μπορεί να φαίνονται διαφορετικά.
<!--
****************************************
*** Αυτό είναι σχολιασμένο μέχρι να ***
*** δημιουργηθεί ένα εκπαιδευτικό ***
*** εγχειρίδιο για τα Windows ***
****************************************
Παρακαλούμε σημειώστε ότι αυτό το εκπαιδευτικό εγχειρίδιο αφορά το MacOS. Παρακαλούμε ανατρέξτε στο [Εκπαιδευτικό Εγχειρίδιο για τα Windows]() για το Sourcetree αν επιθυμείτε να το χρησιμοποιήσετε.
-->
Κατεβάστε το [Sourcetree](https://www.sourcetreeapp.com), εγκαταστήστε το και ανοίξτε το.
Θα πρέπει να δείτε το παράθυρο διαλόγου "Sourcetree".
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-1-main.png" alt="SourceTree Main" />
Από εδώ, θέλετε να κάνετε κλικ στο "Remote" (Απομακρυσμένο). Εάν αυτή είναι η πρώτη εγκατάσταση, τότε πιθανώς δεν έχετε συνδέσει ακόμα τον λογαριασμό σας στο GitHub. Κάντε το κάνοντας κλικ στο κουμπί "Connect" (Σύνδεση).
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-2-main-connect.png" alt="SourceTree Connect" />
Θα εμφανιστεί το παράθυρο διαλόγου *Accounts* (Λογαριασμοί). Κάντε κλικ στο "Add" (Προσθήκη) στην κάτω αριστερή γωνία. Στη συνέχεια, επιλέξτε τις κατάλληλες ρυθμίσεις για να προσθέσετε το GitHub (ή οποιονδήποτε άλλο λογαριασμό θέλετε) στον πελάτη. Αφού επιλέξετε τις ρυθμίσεις σας για το GitHub, κάντε κλικ στο "Connect Account" (Σύνδεση Λογαριασμού).
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-4-accounts-add.png" alt="SourceTree Connect Add" />
Αυτό θα ανοίξει μια σελίδα στον περιηγητή σας. Ακολουθήστε τα βήματα που δίνονται για να εξουσιοδοτήσετε τον λογαριασμό σας.
## Κλωνοποίηση αυτού του αποθετηρίου
Κλωνοποιήστε αυτό το αποθετήριο κάνοντας κλικ στο κουμπί κλωνοποίησης (fork) στην κορυφή αυτής της σελίδας.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/fork.png" alt="fork this repository" />
Αυτό θα δημιουργήσει ένα αντίγραφο αυτού του αποθετηρίου στον λογαριασμό σας.
## Κλωνοποίηση του αποθετηρίου
Στο Sourcetree, κάντε κλικ στο κουμπί "Remote" (Απομακρυσμένο). Αυτό θα φορτώσει όλα τα αποθετήριά σας στο GitHub που εμφανίζονται στο GitHub.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-5-cloning.png" alt="clone this repository" />
Αφού κάνετε κλικ στο κουμπί "Clone" (Κλωνοποίηση), θα εμφανιστεί μια άλλη προβολή για να ορίσετε διάφορα πράγματα.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-6-cloning-confirm.png" alt="clone this repository" />
1) **Διεύθυνση URL πηγής:** Αυτό συμπληρώνεται αυτόματα και δεν χρειάζεται να το αλλάξετε. Είναι η URL από όπου βρίσκεται το έργο σας στο GitHub.
2) **Διαδρομή προορισμού:** Αυτή είναι η φυσική τοποθεσία στον υπολογιστή σας όπου θα αποθηκευτεί το έργο.
3) **Όνομα:** Αυτό είναι ένα "Σελιδοδείκτης" προς τον τρόπο που θα αναφέρεται στο έργο σας ο Sourcetree. Σκεφτείτε το ως μια συντόμευση.
*Σημείωση: Συνήθως οι προεπιλογές σε αυτά τα πεδία είναι καλές.*
**Αφού είστε ικανοποιημένοι, κάντε κλικ στο "Clone" (Κλωνοποίηση)**
Αυτό θα φέρει το κύριο πρόγραμμα περιήγησης του αποθετηρίου σας!
## Δημιουργία κλαδιού (branch)
Κάντε κλικ στο κουμπί κλαδιού στη γραμμή εργαλείων.
Ονομάστε το κλαδί σας "add-your-name-to-contribution", για παράδειγμα: "add-sally-to-contribution".
Για να το κάνετε αυτό, κάντε κλικ στο **Branch (1)** που θα εκκινήσει το παράθυρο ονομασίας. Στη συνέχεια, **Προσθέστε το όνομά σας (2)** όπως μόλις περιγράφηκε. Τέλος, κάντε κλικ στο **Create Branch (Δημιουργία Κλαδιού)**. Αυτό θα δημιουργήσει το κλαδί για ό,τι μόλις ονομάσατε.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-7-branching.png" alt="name your branch" />
## Κάντε τις απαραίτητες αλλαγές και κάντε commit αυτές τις αλλαγές
Τώρα ανοίξτε το αρχείο `Contributors.md` σε έναν επεξεργαστή κειμένου και προσθέστε το όνομά σας σε αυτό, μαζί με το σύνδεσμο του GitHub, και σώστε το αρχείο.
Θα πρέπει να μπορείτε να δείτε και να ελέγξετε το αρχείο που έχει αλλάξει και να αποφασίσετε τι θέλετε να επιλέξετε. Η επιλογή είναι σημαντική για να πείτε στο git ποιες αλλαγές θέλετε να συσχετίσετε με αυτή την προσθήκη.
*Σημείωση: Εάν δεν βλέπετε τη διαφορά του αρχείου, κάντε κλικ στο **Uncommitted Files** (Μη Κοινοποιημένα Αρχεία) στην κορυφή του παραθύρου διαλόγου σας*
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-8-viewing-changed-files.png" alt="edit some file(s)" />
Στη συνέχεια, κάντε κλικ στο κουμπί **Commit (Κοινοποίηση)** στην πάνω αριστερή γωνία του παραθύρου. Αυτό θα σας εμφανίσει την περιοχή σας κοινοποίησης.
Κάντε κλικ στο *Checkbox* για να **προσθέσετε** το αρχείο στην περιοχή κοινοποίησης. Στη συνέχεια, εισαγάγετε ένα μήνυμα κοινοποίησης.
*Σημείωση: Μπορείτε επίσης να επιλέξετε αρχεία (και στις περιοχές κοινοποίησης και μη κοινοποιημένες) και να προσθέσετε/αφαιρέσετε αρχεία από τις αντίστοιχες περιοχές χρησιμοποιώντας το πλήκτρο διαστήματος*
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-9-committing.png" alt="stage your changes" />
Αφού προσθέσετε τις αλλαγές σας και προσθέσετε ένα μήνυμα κοινοποίησης, μπορείτε να πατήσετε το κουμπί **Commit (Κοινοποίηση)** για να κάνετε την κοινοποίηση τελικά.
Συγχαρητήρια, έχετε κοινοποιήσει όλες τις αλλαγές στο τοπικό αντίγραφο του κλαδιού του πιρουνιού (branch) του fork σας των πρώτων συνεισφορών. Μπράβο!
## Μεταφόρτωση (Push) των αλλαγών στο GitHub
Τώρα είστε έτοιμοι να μεταφορτώσετε τις αλλαγές σας στο github. Αυτό θα γίνει μεταφέροντάς το στο δικό σας, το fork, αντίγραφο του έργου. Ακολουθήστε τα βήματα για να μεταφέρετε το πρόγραμμα. Πρώτα, κάντε κλικ στο **Push (Μεταφόρτωση) (1)**, αυτό θα εμφανίσει το παράθυρο απομακρυσμένης/μεταφόρτωσης. **Κάντε κλικ (2)** στο πλαίσιο ελέγχου του κλαδιού που θέλετε να μεταφορτώσετε. Επιλέξτε **OK (3)** και αυτό θα μεταφορτώσει την κοινοποίησή σας στο Github.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/sourcetree-10-pushing.png" alt="origin or branch" />
## Υποβάλετε τις αλλαγές σας για αναθεώρηση
Εάν πάτε στο αποθετήριο σας στο github, θα δείτε το κουμπί `Compare & pull request` (Σύγκριση και αίτηση εξαγωγής). Κάντε κλικ σε αυτό το κουμπί.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/compare-and-pull.png" alt="create a pull request" />
Τώρα υποβάλετε την αίτηση εξαγωγής (pull request).
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sourcetree-macos-tutorial/submit-pull-request.png" alt="submit pull request" />
Σύντομα θα ενσωματώσω όλες τις αλλαγές σας στο κύριο κλαδί (master) αυτού του έργου. Θα λάβετε ένα email ειδοποίησης μόλις οι αλλαγές έχουν ενσωματωθεί.
## Πού να πάτε από εδώ;
Συγχαρητήρια! Έχετε μόλις ολοκληρώσει την τυπική ροή _fork -> clone -> edit -> PR_ που θα αντιμετωπίσετε συχνά ως συνεισφέροντας!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε τη με τους φίλους σας και τους ακόλουθούς σας μεταβαίνοντας στην [ιστοσελίδα εφαρμογής](https://firstcontributions.github.io/#social-share).
Μπορείτε να ενταχθείτε στην ομάδα μας στο Slack εάν χρειάζεστε βοήθεια ή έχετε κάποιες ερωτήσεις. [Ενταχθείτε στην ομάδα Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Πρόσθετο υλικό](../additional-material/git_workflow_scenarios/additional-material.md)
## Οδηγοί με άλλα εργαλεία
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Greek/sublime-merge-tutorial.gr.md
+118
View File
@@ -0,0 +1,118 @@
[![Αγάπη για τον Ανοικτό Κώδικα](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Άδεια: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Βοηθοί Ανοικτού Κώδικα](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Πρώτες Συνεισφορές
|<img alt="Sublime Merge" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sublime-merge.png" width="200">|Sublime Merge Git Client|
|---|---|
Είναι δύσκολο. Είναι πάντα δύσκολο, όταν κάνετε κάτι για πρώτη φορά. Ειδικά όταν συνεργάζεστε ή δοκιμάζετε κάτι νέο, τα λάθη δεν είναι ένα άνετο πράγμα. Αλλά ο ανοικτός κώδικας αφορά την συνεργασία και την ομαδική εργασία. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο οι νέοι συνεισφέροντες ανοικτού κώδικα μαθαίνουν και συνεισφέρουν για πρώτη φορά.
Η ανάγνωση άρθρων και η παρακολούθηση εκπαιδευτικού υλικού μπορεί να βοηθήσουν, αλλά τι είναι καλύτερο από το να κάνετε πράγματα στην πράξη χωρίς να χαλάσετε τίποτα. Αυτό το έργο στοχεύει στην παροχή καθοδήγησης και στην απλοποίηση του τρόπου με τον οποίο οι νεοσύστατοι συνεισφέροντες κάνουν την πρώτη τους συνεισφορά. Θυμηθείτε ότι όσο πιο χαλαροί είστε, τόσο καλύτερα μαθαίνετε. Αν ψάχνετε για να κάνετε την πρώτη σας συνεισφορά, ακολουθήστε απλά τα απλά βήματα παρακάτω. Σας υποσχόμαστε, θα είναι διασκεδαστικό.
## Sublime Merge
Κατεβάστε το [Sublime Merge](https://www.sublimemerge.com/), εγκαταστήστε το και ανοίξτε το.
## Διακλάδωση (Fork) αυτού του αποθετηρίου
Κάντε διακλάδωση (fork) αυτού του αποθετηρίου κάνοντας κλικ στο κουμπί διακλάδωσης (fork) στην κορυφή αυτής της σελίδας.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/fork.png" alt="fork this repository" />
Αυτό θα δημιουργήσει ένα αντίγραφο αυτού του αποθετηρίου στον λογαριασμό σας.
<br>
<br>
<br>
<br>
## Κλωνοποίηση (Clone) του αποθετηρίου
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/clone.png" alt="clone this repository" />
Στο Sublime Merge, πηγαίνετε στο Αρχείο -> Κλωνοποίηση (Clone) αποθετηρίου.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-clone.png" alt="clone this repository" />
Το επόμενο βήμα είναι να κλωνοποιήσετε το αποθετήριο σας στον υπολογιστή σας, ώστε να μπορείτε να αρχίσετε να κάνετε αλλαγές. Το Sublime Merge χρειάζεται το URL του αποθετηρίου σας, οπότε κάντε κλικ στο κουμπί "κλωνοποίηση" και στη συνέχεια κάντε κλικ στο εικονίδιο "αντιγραφή στο πρόχειρο".
**ΠΡΟΣΟΧΗ:** Ένα λάθος που συχνά κάνουν οι νέοι συνεισφέροντες είναι να κλωνοποιούν το αποθετήριο από το οποίο έχουν κάνει fork _αντί να κλωνοποιούν το δικό τους αποθετήριο_. Ελέγξτε τη γραμμή διεύθυνσης του προγράμματος περιήγησής σας και βεβαιωθείτε ότι κλωνοποιείτε το δικό σας αποθετήριο.
Εισάγετε το URL του αποθετηρίου στο Sublime Merge, δώστε του ένα όνομα αποθετηρίου (ή αφήστε το κενό) και ορίστε τον κατάλογο όπου θα αποθηκευτεί το αποθετήριο.
Αφού είστε ικανοποιημένοι με το μονοπάτι, κάντε κλικ στο "Κλωνοποίηση".
## Δημιουργία παρακλαδιού (Branch)
Κάντε δεξί κλικ στο Branches -> Δημιουργία Παρακλαδιού
ή
Πλοηγηθείτε στο Αποθετήριο -> Δημιουργία Παρακλαδιού
Δώστε όνομα στο παρακλάδι σας "προσθήκη-του-όνοματός-σας", για παράδειγμα: "προσθήκη-της-Άννας-Σοφίας"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-branch.png" alt="name your branch" />
## Κάντε τις απαραίτητες αλλαγές και κοινοποιήστε τις αλλαγές αυτές
Τώρα ανοίξτε το αρχείο `Contributors.md` σε έναν επεξεργαστή κειμένου και προσθέστε το όνομά σας, στη συνέχεια αποθηκεύστε το αρχείο.
Εάν έχετε το αποθετήριο ανοιχτό στο Sublime Merge, θα δείτε ότι υπάρχουν αλλαγές.
Επιλέξτε την πιο πρόσφατη κοινοποίηση στην κορυφή, που έχει όνομα "x unstaged αρχεία"
Ελέγξτε τα αρχεία που έχουν αλλάξει και αποφασίστε ποια θέλετε να κάνετε stage.
Δώστε στην κοινοποίηση ένα μήνυμα ("Προσθήκη του <το-όνομά-σας> στη λίστα Συνεισφερόντων" ακούγεται ωραίο και περιγραφικό).
Όταν είστε ικανοποιημένοι με τις αλλαγές σας, κοινοποιήστε αυτές τις αλλαγές κάνοντας τες stage αρχείο-αρχείο ή επιλέγοντας "stage all". Το staging είναι σημαντικό για να πείτε στο git ακριβώς ποιες αλλαγές αρχείων θέλετε να συσχετίσετε με αυτήν την κοινοποίηση.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-stage.png" alt="stage your changes" />
Εάν αλλάξετε γνώμη, μπορείτε να αφαιρέσετε αυτές τις αλλαγές, ή μπορείτε να τις απορρίψετε εντελώς.
ΠΡΟΕΙΔΟΠΟΙΗΣΗ: Όπως υποδηλώνει η λέξη "απόρριψη", αυτή είναι μια καταστροφική λειτουργία. Κάντε αυτό μόνο εάν δεν θέλετε καμία αλλαγή από το οποιοδήποτε αποθετήριο βρίσκεστε.
Κάντε κλικ στο κουμπί "Κοινοποίηση" στο επάνω αριστερό μέρος της προκαθορισμένης συνομιλίας. Αυτό θα σας δείξει την περιοχή σας που έχει κοινοποιηθεί.
Κάντε κλικ στο *κουτάκι επιλογής* για να **προσθέσετε** το αρχείο στη σκηνή. Στη συνέχεια, εισαγάγετε ένα μήνυμα κοινοποίησης.
*Σημείωση: Μπορείτε επίσης να επιλέξετε αρχεία (και στις περιοχές με κοινοποίηση και μη κοινοποίηση) και να προσθέσετε/αφαιρέσετε αρχεία από τις αντίστοιχες περιοχές χρησιμοποιώντας το πλήκτρο διαστήματος.*
Αφού προσθέσετε τις αλλαγές σας και προσθέσετε ένα μήνυμα κοινοποίησης, μπορείτε να πατήσετε το κουμπί "Κοινοποίηση" για να κάνετε την τελική κοινοποίηση.
Συγχαρητήρια, έχετε κοινοποιήσει όλες τις αλλαγές στo τοπικό αντίγραφο του παρακλαδιού σας του αποθετηρίου που έχετε κάνει fork. Συνεχίζουμε!
## Αποστολή των αλλαγών στο GitHub
Τώρα είστε έτοιμοι να στείλετε τις αλλαγές σας στο GitHub. Αυτό θα τις στείλει στο δικό σας, διακλαδωμένο, αντίγραφο του έργου.
Πλοηγηθείτε στο Αποθετήριο -> Αποστολή (Push)
ή πατήστε το μικρό βέλος προς τα πάνω στη δεξιά πάνω γωνία.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/sm-login.png" alt="login" />
Συνδεθείτε στον λογαριασμό σας στο Github με το όνομα χρήστη και τον κωδικό πρόσβασής σας.
Καταθέστε τις αλλαγές στο παρακλάδι origin εάν θέλετε να εμφανίζονται οι αλλαγές στο παρακλάδι master απευθείας, διαφορετικά επιλέξτε το κατάλληλο παρακλάδι που θέλετε να στείλετε.
## Υποβολή των αλλαγών σας για αξιολόγηση
Εάν πάτε στο αποθετήριο σας στο Github, θα δείτε το κουμπί `Σύγκριση και αίτηση ενσωμάτωσης` (Compare & pull request). Κάντε κλικ σε αυτό το κουμπί.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/sublime-merge-tutorial/compare-and-pull.png" alt="create a pull request" />
Τώρα υποβάλετε το αίτημα ενσωμάτωσης (pull request).
Κάντε κλικ στο κουμπί `Υποβολή αιτήματος ενσωμάτωσης` (Submit pull request).
Σύντομα θα ενσωματώσω όλες τις αλλαγές σας στον παρακλάδι master αυτού του έργου. Θα λάβετε ένα email ειδοποίησης μόλις οι αλλαγές έχουν ενσωματωθεί.
## Τι να κάνετε μετά;
Συγχαρητήρια! Έχετε μόλις ολοκληρώσει την τυπική ροή εργασίας _fork -> clone -> edit -> PR_ που θα συναντήσετε συχνά ως συνεισφέρων!
Γιορτάστε τη συνεισφορά σας και μοιραστείτε τη με τους φίλους και τους ακόλουθούς σας, πηγαίνοντας στην [ιστοσελίδα εφαρμογής](https://firstcontributions.github.io#social-share).
Μπορείτε επίσης να εγγραφείτε στην ομάδα μας στο Slack αν χρειαστείτε βοήθεια ή έχετε ερωτήσεις. [Εγγραφή στην ομάδα Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Επιπλέον υλικό](../additional-material/git_workflow_senarios/additional-material.md)
## Εκπαιδευτικό υλικό για Άλλα Εργαλεία
[Επιστροφή στην κύρια σελίδα](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Hindi/github-windows-vs-code-tutorial-hi.md
+116
View File
@@ -0,0 +1,116 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/CodeWithAjaySaini)
# First Contributions
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
यह मुश्किल है। पहली बार जब आप कुछ करते हैं तो यह हमेशा कठिन होता है। खासकर जब आप सहयोग कर रहे हों, तो गलतियाँ करना सहज बात नहीं है। लेकिन ओपन सोर्स सहयोग और एक साथ काम करने के बारे में है। हम नए ओपन-सोर्स योगदानकर्ताओं के पहली बार सीखने और योगदान करने के तरीके को सरल बनाना चाहते थे।
लेख पढ़ना और ट्यूटोरियल देखना मदद कर सकता है, लेकिन वास्तव में कुछ भी गड़बड़ किए बिना सामान करने से बेहतर क्या हो सकता है। इस परियोजना का उद्देश्य मार्गदर्शन प्रदान करना और धोखेबाज़ों द्वारा अपना पहला योगदान देने के तरीके को सरल बनाना है। याद रखें कि आप जितने अधिक आराम से होंगे, आप उतना ही बेहतर सीखेंगे। यदि आप अपना पहला योगदान करना चाहते हैं, तो बस नीचे दिए गए सरल चरणों का पालन करें। हम आपसे वादा करते हैं, यह मजेदार होगा।
यदि आपकी मशीन पर विजुअल स्टूडियो कोड नहीं है, [install it](https://code.visualstudio.com/download).
**सूचना:** यह ट्यूटोरियल विंडोज 10 मशीन पर विजुअल स्टूडियो कोड (संस्करण 1.27.2) का उपयोग करके बनाया गया था। बाद में इस ट्यूटोरियल में हम कुछ कीबोर्ड शॉर्टकट का उपयोग करेंगे। ये अन्य ऑपरेटिंग सिस्टम (मैकोज़/लिनक्स) के साथ-साथ कीबोर्ड भाषा (यूके, डीई, आदि) पर भिन्न हो सकते हैं। आप कमांड पैलेट में "शॉर्टकट" खोजकर अपने शॉर्टकट की सूची देख सकते हैं।
## इस भंडार को फोर्क करें
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
इस रेपो को फोर्क करने के लिए इस पेज के ऊपर दाईं ओर फोर्क बटन पर क्लिक करें। यह आपके GitHub खाते में इस रिपॉजिटरी की एक प्रति बनाएगा।
गिटहब आपके रेपो और उस रेपो के बीच संबंधों का ट्रैक रखता है जिसे आपने इसे फोर्क किया है। आप अपने रेपो को एक कार्यशील प्रति के रूप में सोच सकते हैं।
अधिकांश शीर्ष-स्तरीय गिटहब रेपो (यानी किसी अन्य रेपो से फोर्क नहीं किए गए) में लोगों की एक छोटी सी कोर टीम होती है जो सीधे बदलाव कर सकती है। अन्य सभी योगदानकर्ताओं को रेपो को फोर्क करना होगा और फोर्क में परिवर्तन करना होगा, फिर एक पुल अनुरोध बनाना होगा ताकि उनके परिवर्तनों को शीर्ष-स्तरीय रेपो में वापस विलय करने के लिए कहा जा सके। यदि शीर्ष-स्तरीय रेपो व्यवस्थापक परिवर्तनों को पसंद करता है तो उन्हें विलय कर दिया जाएगा और आपको तुरंत प्रसिद्धि और भाग्य प्राप्त होगा! इसे बाद में कैसे करें, इसके बारे में अधिक।
## अपने भंडार को क्लोन करें
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
अगला कदम अपने रेपो को अपनी मशीन पर क्लोन करना है ताकि आप बदलाव करना शुरू कर सकें। वीएस कोड को आपके रेपो के यूआरएल की जरूरत है, इसलिए "क्लोन" बटन पर क्लिक करें और फिर "क्लिपबोर्ड पर कॉपी करें" आइकन पर क्लिक करें।
**सावधान:** एक गलती जो नए योगदानकर्ता अक्सर करते हैं, वह है रेपो का क्लोन बनाना जो आपने अपने रेपो को क्लोन करने के बजाय _from_ को फोर्क किया था। अपने ब्राउज़र के एड्रेस बार की जाँच करें और सुनिश्चित करें कि आप अपने रेपो की क्लोनिंग कर रहे हैं।
अब विजुअल स्टूडियो कोड खोलें। वीएस कोड का वेलकम पेज खुल जाएगा। वहां से नीचे दिखाए गए बार को खोलने के लिए `F1` दबाएं। ध्यान दें कि टेक्स्ट फ़ील्ड में पहले से ही एक `>` (इससे बड़ा) चिन्ह है। आप `CTRL-P` दबाकर इनपुट प्रॉम्प्ट पर भी जा सकते हैं और फिर `>` वर्ण टाइप कर सकते हैं।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
आप देख सकते हैं कि नीचे सूचीबद्ध कुछ अस्पष्ट आदेश पहले से ही हैं। वे मेरे हाल ही में उपयोग किए गए आदेश हैं। तो बस उनकी परवाह मत करो।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
अब 'गिट क्लोन' टाइप करें, केवल 'गिट' या 'क्लोन' (यह एक खोज की तरह काम करता है)।
प्रविष्टि `गिट: क्लोन` का चयन करें और `एंटर` दबाएं
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
अपनी रिपॉजिटरी का URL पेस्ट करें और `Enter` दबाएं। यह एक फ़ाइल एक्सप्लोरर खोलेगा जहाँ आप तब चुन सकते हैं जहाँ Git रिपॉजिटरी को संग्रहीत किया जाना चाहिए।
**महत्वपूर्ण**: सुनिश्चित करें कि यह फोर्कड रिपोजिटरी है और मूल नहीं है, अन्यथा यह काम नहीं करेगा।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
आपको विजुअल स्टूडियो कोड के नीचे दाईं ओर एक स्टेटस पॉपअप देखना चाहिए। इसके समाप्त होने के बाद, आप संवाद में बटनों का उपयोग करके क्लोन रिपॉजिटरी (अब आपकी मशीन पर एक फ़ोल्डर) खोल सकते हैं।
## एक शाखा बनाएं
`F1` दबाकर फिर से कमांड पैलेट खोलें। `शाखा` टाइप करें और वहां से `शाखा बनाएं` कमांड चुनें। अगले चरण में अपनी नई शाखा का नाम टाइप करें, उदाहरण के लिए `ऐड-डेविड-क्रोल`। एंटर दबाएं और ब्रांच बन जाएगी. The branch is also already checked out. [What does checkout mean?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## आवश्यक परिवर्तन करें
`Contributors.md` खोलें और फ़ाइल में कहीं भी अपना नाम जोड़ें। इस फ़ाइल में GFM (GitHub Flavored Markdown) है जो <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a> सिंटैक्स का मालिकाना स्वाद है।
अन्य योगदानकर्ताओं में से एक की प्रतिलिपि बनाएँ&apos; लाइनों और इसे अपने नाम के साथ संशोधित करें यह सुनिश्चित करने के लिए कि आपको सिंटैक्स सही मिलता है - यह पिक्य हो सकता है।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## गिटहब में बदलाव करें और पुश करें
वीएस कोड के बाईं ओर एक मेनू है जिसमें 5 आइकन प्रदर्शित होते हैं। संस्करण नियंत्रण/स्रोत नियंत्रण चिह्न का चयन करें।
(शॉर्टकट : Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
फ़ाइल एक्सप्लोरर उन सभी फाइलों को प्रदर्शित करता है जिन्हें अंतिम प्रतिबद्धता के बाद बदल दिया गया था। फाइलों को मँडराकर और `+` (प्लस) पर क्लिक करके फाइलों का मंचन किया जाता है।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
एक्सप्लोरर के ऊपर लाइन में कुछ टाइप करें और चेकमार्क दबाएं। परिवर्तन अब आपकी स्थानीय प्रति के लिए प्रतिबद्ध हैं। अब परिवर्तनों को वापस GitHub पर धकेलना होगा।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
मेनू खोलने के लिए थ्री-डॉट आइकन का उपयोग करें जहां आप `पब्लिश ब्रांच` विकल्प का चयन करते हैं। यह आपके GitHub क्रेडेंशियल्स को डालने के लिए एक डायलॉग खोलना चाहिए।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="स्टैश की गई फ़ाइलें ">
## समीक्षा के लिए अपने परिवर्तन सबमिट करें
इस बिंदु पर आपने अपना परिवर्तन पूरा कर लिया है लेकिन यह अभी भी केवल आपके रेपो में रहता है। यह चरण आपको दिखाएगा कि अपने परिवर्तन को मर्ज करने के लिए शीर्ष-स्तरीय रेपो के व्यवस्थापक को अनुरोध कैसे सबमिट करें।
गिटहब पर अपने रेपो में आपको नई शाखा अधिसूचना के बगल में `तुलना और पुल अनुरोध` बटन दिखाई देगा। उस बटन पर क्लिक करें।
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="एक पुल अनुरोध बनाएं" />
अब पुल रिक्वेस्ट सबमिट करें।
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="पुल अनुरोध सबमिट करें" />
जल्द ही मैं आपके सभी परिवर्तनों को इस परियोजना की मास्टर शाखा में मिला दूंगा। परिवर्तनों को मर्ज कर दिए जाने के बाद आपको एक सूचना ईमेल प्राप्त होगी।
## यहाँ से कहाँ जाएं?
बधाई! आपने अभी-अभी मानक _fork -> क्लोन -> संपादित करें -> PR_ वर्कफ़्लो पूरा किया है जिसका आप अक्सर एक योगदानकर्ता के रूप में सामना करेंगे!
अपने योगदान का जश्न मनाएं और [वेब ऐप](https://firstcontributions.github.io#social-share) पर जाकर इसे अपने दोस्तों और अनुयायियों के साथ साझा करें।
यदि आपको किसी सहायता की आवश्यकता हो या कोई प्रश्न पूछना हो तो आप हमारी सुस्त टीम में शामिल हो सकते हैं। [स्लैक टीम में शामिल हों](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)।
### [अतिरिक्त सामग्री](../additional-material/git_workflow_scenarios/additional-material.md)
## अन्य टूल्स का उपयोग करने वाले ट्यूटोरियल
[मुख्य पृष्ठ पर वापस जाएं](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Indonesian/github-windows-vs-code-tutorial_id.md
+121
View File
@@ -0,0 +1,121 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Kontribusi Pertama
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
Sulit. Memang selalu sulit melakukan sesuatu untuk pertama kali. Khususnya ketika kamu berkolaborasi, membuat sebuah masalah bukanlah hal yang mengenakkan. Tetapi proyek terbuka
berarti kolaborasi dan kerjasama. Kami ingin menyederhanakan cara belajar bagi kontributor dan cara berkontribusi untuk pertama kali.
Membaca artikel & menonton tutorial bisa membantu, tetapi lebih baik praktek langsung tanpa membuat masalah apapun pada proyek. Laman ini bertujuan untuk memberikan panduan & menyederhanakan cara bagi pemula untuk membuat kontribusi pertama. Ingat semakin santai kamu, maka semakin baik kamu belajar. Jika kamu ingin membuat kontribusi pertama, cukup ikuti langkah-langkah sederhana di bawah ini. Kami janji, ini akan menyenangkan kok.
Jika kamu belum punya Visual Studio Code pada perangkat mu, [install disini](https://code.visualstudio.com/download).
**Perlu Diingat:** Tutorial ini dibuat menggunakan Visual Studio Code (Versi 1.27.2) pada Windows 10. Nanti dalam tutorial ini kita akan menggunakan beberapa shortcut keyboard. Ini mungkin berbeda pada sistem operasi lain (macOS/Linux) serta bahasa keyboard (UK, DE, dll). Kamu dapat menelusuri daftar pintasan mu dengan mencari "shortcut" di Palet Perintah.
## Fork repositori ini
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Fork repo ini dengan mengklik tombol fork di kanan atas halaman ini. Ini akan membuat salinan repositori ini di akun GitHub Anda.
GitHub selalu menjaga repo mu dan sumber repo yang sudah kamu fork supaya tetap pada jalurnya. Kamu bisa menganggap repo mu sebagai salinan pekerjaan.
Sebagian besar repo GitHub tingkat atas (yaitu yang tidak di-copy dari repo lain mana pun) mempunyai tim inti yang terdiri dari orang-orang yang dapat langsung melakukan perubahan. Semua kontributor lain harus melakukan fork repo dan membuat perubahan pada fork, lalu membuat Pull Request untuk meminta perubahan mereka digabungkan kembali ke repo tingkat atas. Jika administrator repo tingkat atas menyukai perubahan, mereka akan menggabungkan perubahan mu dan kamu bisa mendapatkan reputasi dan nasib baik! Lebih lanjut tentang cara melakukannya akan dibahas nanti.
## Klon Repositori mu
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
Langkah selanjutnya adalah mengkloning repo mu ke perangkat mu sehingga bisa segera mulai membuat perubahan. VS Code membutuhkan URL repo mu agar terhubung, jadi klik tombol "clone" dan kemudian klik ikon "copy to clipboard".
**HATI-HATI:** Satu kesalahan yang sering dilakukan oleh kontributor baru adalah mengkloning repo utama yang kamu fork _sumbernya_ daripada mengkloning repo mu sendiri. Periksa alamat browser mu dan pastikan kamu mengkloning repo mu sendiri.
Sekarang buka Visual Studio Code. Halaman selamat datang dari VS Code akan muncul. Dari sana tekan `F1` untuk membuka bar yang ditunjukkan di bawah ini. Perhatikan bahwa sudah ada tanda `>` (lebih besar dari) di kolom teks. Anda juga dapat membuka input prompt dengan menekan `CTRL-P` lalu ketik `>`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Anda mungkin memperhatikan bahwa sudah ada beberapa perintah tidak jelas yang tercantum di bawah ini. Itu adalah perintah yang digunakan baru-baru ini. Jadi, hiraukan saja.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Sekarang ketik `git clone`, hanya `git` atau `clone` (berfungsi seperti melakukan pencarian).
Pilih Entri `Git: Clone` dan tekan `Enter`
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
Tempelkan URL repositori kamu dan tekan `Enter`. Ini akan membuka File Explorer di mana kamu dapat memilih di mana repositori Git harus disimpan
**Penting**: Pastikan itu adalah repositori yang kamu fork dan bukan yang asli, jika tidak maka tidak akan berfungsi
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Kamu akan melihat status popup di kanan bawah Visual Studio Code. Setelah selesai, kamu dapat membuka repositori kloning (di folder yang sudah kamu pilih) menggunakan tombol di dialog.
## Membuat Cabang (Branch)
Buka kembali palet perintah dengan menekan `F1`. Ketik `branch` dan pilih perintah `create branch` dari sana. Pada langkah berikutnya ketik nama cabang baru kamu, misalnya `add-david-kroell`. Tekan enter dan cabang akan dibuat. Cabang juga sudah siap dipakai. [Apa artinya checkout?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Buat Perubahan yang diperlukan
Buka `Contributors.md` dan tambahkan nama kamu di mana saja di file. File ini berisi GFM (GitHub Flavoured Markdown) yang merupakan ciri khas sintaks <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Salin salah satu kontributor lain&apos; baris dan modifikasi dengan nama mu untuk memastikan kamu menggunakan sintaks yang benar - itu bisa pilih-pilih
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Commit & Push perubahan ke GitHub
Di sisi kiri VS Code adalah menu dengan 5 ikon yang ditampilkan. Pilih ikon versi kontrol/Sumber Kontrol.
(Pintasan: Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
File explorer menampilkan semua file yang diubah setelah komit terakhir. Dengan mengarahkan penunjuk pada file dan mengklik `+` (plus) file akan disiapkan.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
Ketik sesuatu pada baris di atas explorer dan tekan tanda centang. Perubahan telah tersimpan pada salinan lokal kamu. Sekarang perubahan harus di _push_ kembali ke GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
Gunakan ikon titik tiga untuk membuka menu tempat kamu akan memilih opsi `Publish Branch`. Ini akan membuka dialog untuk memasukkan kredensial GitHub kamu.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## Submit perubahan mu untuk diperiksa
Dititik ini kamu telah menyelesaikan perubahan mu tetapi masih berada di repo mu sendiri. Langkah ini akan menunjukkan bagaimana cara mengirimkan permintaan ke administrator repo tingkat atas untuk menggabungkan perubahan
Pada repo mu di GitHub, kamu akan melihat tombol `Compare & pull request` di sebelah pemberitahuan cabang baru. Klik tombol itu.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Sekarang kirimkan permintaan _pull_.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Segera saya akan menggabungkan semua perubahan mu ke dalam cabang utama proyek ini. Kamu akan mendapatkan email pemberitahuan setelah perubahan digabungkan.
## Kemana lagi setelah ini?
Selamat! kamu baru saja menyelesaikan alur kerja _fork -> clone -> edit -> PR_ standar yang akan sering kamu temui sebagai kontributor!
Rayakan kontribusi mu dan bagikan dengan teman dan pengikut kamu dengan membuka [web app](https://firstcontributions.github.io#social-share).
Kamu dapat bergabung dengan tim slack kami jika memerlukan bantuan atau memiliki pertanyaan. [Bergabung dengan tim Slack](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
### [ Materi tambahan ](../../additional-material/translations/additional-material.id.md)
## Tutorial menggunakan Alat lain
[Kembali ke halaman utama](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Marathi/github-windows-vs-code-tutorial-hi.md
+116
View File
@@ -0,0 +1,116 @@
[![मुक्त स्रोत प्रेम](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/CodeWithAjaySaini)
#प्रथम योगदान
, <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/2/2d/Visual_Studio_Code_1.18_icon.svg" width="40"> | व्हिज्युअल स्टुडिओ कोड |
, , ,
हे अवघड आहे. तुम्ही पहिल्यांदा काहीतरी करता ते नेहमीच कठीण असते. विशेषत: तुम्ही सहयोग करत असताना, चुका करणे सोपे नसते. पण ओपन सोर्स हे सहकार्य आणि एकत्र काम करण्याबद्दल आहे. आम्हाला नवीन मुक्त-स्रोत योगदानकर्त्यांसाठी प्रथमच शिकण्याचा आणि योगदान देण्याचा मार्ग सोपा करायचा होता.
लेख वाचणे आणि ट्यूटोरियल पाहणे मदत करू शकते, परंतु काहीही गोंधळ न करता प्रत्यक्षात सामग्री करण्यापेक्षा काय चांगले आहे. या प्रकल्पाचे उद्दिष्ट मार्गदर्शन प्रदान करणे आणि धोकेबाजांना त्यांचे प्रथम योगदान देण्यासाठी मार्ग सुलभ करणे आहे. लक्षात ठेवा की तुम्ही जितके निवांत राहाल तितके चांगले शिकाल. तुम्हाला तुमचे पहिले योगदान करायचे असल्यास, फक्त खालील सोप्या चरणांचे अनुसरण करा. आम्ही तुम्हाला वचन देतो, ते मजेदार असेल.
तुमच्या मशीनवर व्हिज्युअल स्टुडिओ कोड नसल्यास, [तो स्थापित करा](https://code.visualstudio.com/download).
**टीप:** हे ट्यूटोरियल Windows 10 मशीनवर व्हिज्युअल स्टुडिओ कोड (आवृत्ती 1.27.2) वापरून तयार केले गेले आहे. नंतर या ट्युटोरियलमध्ये आपण काही कीबोर्ड शॉर्टकट वापरू. हे इतर ऑपरेटिंग सिस्टीम (MacOS/Linux) तसेच कीबोर्ड भाषा (UK, DE, इ.) वर बदलू शकतात. कमांड पॅलेटमध्ये "शॉर्टकट" शोधून तुम्ही तुमच्या शॉर्टकटची यादी पाहू शकता.
##या भांडाराचा फोर्क करा
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
हा रेपो फोर्क करण्यासाठी, या पृष्ठाच्या वरच्या उजव्या बाजूला असलेल्या फोर्क बटणावर क्लिक करा. हे तुमच्या GitHub खात्यामध्ये या भांडाराची एक प्रत तयार करेल.
GitHub तुमचा रेपो आणि तुम्ही ज्या रेपो मधून फॉर्क केले आहे त्यामधील संबंधांचा मागोवा ठेवतो. तुम्ही तुमच्या रेपोचा एक कार्यरत प्रत म्हणून विचार करू शकता.
बर्‍याच उच्च-स्तरीय GitHub रेपोमध्ये (म्हणजे दुसर्‍या रेपोमधून काटे काढलेले नाहीत) लोकांची एक लहान कोर टीम असते जी थेट बदल करू शकतात. इतर सर्व योगदानकर्त्यांनी रेपो फोर्क करणे आवश्यक आहे आणि फोर्कमध्ये बदल करणे आवश्यक आहे, त्यानंतर त्यांच्या बदलांना पुन्हा उच्च-स्तरीय रेपोमध्ये विलीन करण्याची विनंती करणारी पुल विनंती तयार करणे आवश्यक आहे. जर उच्च-स्तरीय रेपो प्रशासकाला बदल आवडले तर ते विलीन केले जातील आणि तुम्हाला झटपट प्रसिद्धी आणि नशीब मिळेल! हे कसे करायचे ते नंतर अधिक.
## तुमचा रेपॉजिटरी क्लोन करा
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="हे भांडार क्लोन करा" />
पुढील पायरी म्हणजे तुमचा रेपो तुमच्या मशीनवर क्लोन करणे म्हणजे तुम्ही बदल करणे सुरू करू शकता. VS कोडला तुमच्या रेपोच्या URL ची आवश्यकता आहे, म्हणून "क्लोन" बटणावर क्लिक करा आणि नंतर "क्लिपबोर्डवर कॉपी करा" चिन्हावर क्लिक करा.
**सावधगिरी:** नवीन योगदानकर्ते अनेकदा आपल्या स्वतःच्या रेपोचे क्लोनिंग करण्याऐवजी तुम्ही _from_ फोर्क केलेले रेपो क्लोन करणे ही चूक करतात. तुमच्या ब्राउझरचा अॅड्रेस बार तपासा आणि तुम्ही तुमचा रेपो क्लोन करत असल्याची खात्री करा.
आता व्हिज्युअल स्टुडिओ कोड उघडा. व्हीएस कोडचे स्वागत पृष्ठ उघडेल. तेथून खाली दाखवलेला बार उघडण्यासाठी `F1` दाबा. लक्षात ठेवा मजकूर फील्डमध्ये आधीपासूनच `>` (त्यापेक्षा मोठे) चिन्ह आहे. तुम्ही `CTRL-P` दाबून इनपुट प्रॉम्प्टवर देखील जाऊ शकता आणि नंतर `>` अक्षर टाइप करू शकता.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="क्लोन पॉपअप (कमांड) पॉपअप)" />
तुमच्या लक्षात येईल की खाली सूचीबद्ध केलेल्या काही अस्पष्ट आज्ञा आहेत. त्या माझ्या अलीकडे वापरलेल्या कमांड्स आहेत. त्यामुळे फक्त त्यांची काळजी करू नका.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="क्लोन रेपो" / >
आता 'गिट क्लोन' टाइप करा, फक्त 'गिट' किंवा 'क्लोन' (हे शोधासारखे कार्य करते).
एंट्री `git:clone` निवडा आणि `Enter` दाबा
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="मध्ये भांडार URL पेस्ट करा " />
तुमच्या भांडाराची URL पेस्ट करा आणि 'एंटर' दाबा. हे एक फाईल एक्सप्लोरर उघडेल जिथे तुम्ही गिट रेपॉजिटरी कुठे संग्रहित करावी हे निवडू शकता.
**महत्त्वाचे**: ते फोर्क केलेले भांडार आहे आणि मूळ नाही याची खात्री करा, अन्यथा ते कार्य करणार नाही.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="स्थिती पॉपअप" / >
तुम्हाला व्हिज्युअल स्टुडिओ कोडच्या तळाशी उजवीकडे स्टेटस पॉपअप दिसेल. ते पूर्ण झाल्यानंतर, तुम्ही डायलॉगमधील बटणे वापरून क्लोन केलेले भांडार (आता तुमच्या मशीनवरील फोल्डर) उघडू शकता.
## एक शाखा तयार करा
'F1' दाबून कमांड पॅलेट पुन्हा उघडा. 'शाखा' टाइप करा आणि तिथून 'शाखा तयार करा' कमांड निवडा. पुढील चरणात तुमच्या नवीन शाखेचे नाव टाइप करा, उदाहरणार्थ `add-david-kroll`.एंटर दाबा आणि शाखा तयार होईल. शाखा देखील आधीच तपासली आहे. [चेकआउट म्हणजे काय?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="शाखा कमांड पॅलेट" />
## आवश्यक बदल करा
`Contributors.md` उघडा आणि फाइलमध्ये कुठेही तुमचे नाव जोडा. या फाइलमध्ये GFM (GitHub Flavored Markdown) आहे जी <a href="https://en.wikipedia.org/wiki/Markdown">मार्कडाउन</a> सिंटॅक्सची मालकी आहे.
इतर योगदानकर्त्यांपैकी एक कॉपी करा&apos; ओळी करा आणि तुम्हाला वाक्यरचना योग्य असल्याची खात्री करण्यासाठी तुमच्या नावासह ते सुधारित करा - ते निवडक असू शकते.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="तुमचे नाव जोडा" />
## GitHub मध्ये बदल करा आणि पुश करा
VS कोडच्या डाव्या बाजूला 5 चिन्ह दाखवणारा मेनू आहे. आवृत्ती नियंत्रण/स्रोत नियंत्रण चिन्ह निवडा.
(शॉर्टकट: Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="बदल वचन द्या" / >
फाईल एक्सप्लोरर शेवटच्या कमिटपासून बदललेल्या सर्व फायली प्रदर्शित करतो. फाइल्सवर फिरवून आणि `+` (प्लस) वर क्लिक करून फाईल्स स्टेज केल्या जातात.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
एक्सप्लोररच्या शीर्षस्थानी असलेल्या ओळीत काहीतरी टाइप करा आणि चेकमार्क दाबा. बदल आता तुमच्या स्थानिक प्रतीसाठी वचनबद्ध आहेत. आता बदल GitHub वर ढकलले जाणे आवश्यक आहे.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
मेनू उघडण्यासाठी तीन-बिंदू चिन्ह वापरा जिथे तुम्ही `शाखा प्रकाशित करा` पर्याय निवडता. तुमची GitHub क्रेडेन्शियल एंटर करण्यासाठी याने संवाद उघडला पाहिजे.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stash की गेलेल्या फाईल्स ">
##तुमचे बदल पुनरावलोकनासाठी सबमिट करा
या टप्प्यावर तुम्ही तुमचा बदल पूर्ण केला आहे परंतु तो अजूनही तुमच्या रेपोमध्येच राहतो. हे चरण तुम्हाला तुमचे बदल विलीन करण्यासाठी उच्च-स्तरीय रेपोच्या प्रशासकाकडे विनंती कशी सबमिट करायची ते दर्शवेल.
GitHub वरील तुमच्या रेपोमध्ये तुम्हाला नवीन शाखेच्या अधिसूचनेशेजारी `तुलना आणि पुल विनंती` बटण दिसेल. त्या बटणावर क्लिक करा.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="पुल विनंती तयार करा" />
आता पुल विनंती सबमिट करा.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="पुल विनंती सबमिट करा" />
लवकरच मी तुमचे सर्व बदल या प्रकल्पाच्या मुख्य शाखेत विलीन करीन. एकदा बदल विलीन झाल्यानंतर तुम्हाला एक सूचना ईमेल प्राप्त होईल.
## इथून कुठे जायचं?
अभिनंदन! तुम्ही नुकतेच मानक _fork -> क्लोन -> संपादन -> PR_ वर्कफ्लो पूर्ण केले आहे ज्याचा तुम्हाला अनेकदा एक योगदानकर्ता म्हणून सामना करावा लागेल!
तुमचे योगदान साजरे करा आणि [वेब अॅप](https://firstcontributions.github.io#social-share) ला भेट देऊन ते तुमच्या मित्र आणि अनुयायांसह शेअर करा.
तुम्हाला कोणत्याही सहाय्याची आवश्यकता असल्यास किंवा काही प्रश्न असल्यास, तुम्ही आमच्या स्लॅक टीममध्ये सामील होऊ शकता. [स्लॅक टीममध्ये सामील व्हा](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [अतिरिक्त साहित्य](../additional-material/git_workflow_scenarios/additional-material.md)
##इतर साधनांचा वापर करून शिकवण्या
[मुख्य पृष्ठावर परत](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Persian/github-desktop-tutorial.fa.md
+118
View File
@@ -0,0 +1,118 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# اولین مشارکت
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
همیشه اولین بار سخت‌ترین بار هست. به خصوص زمانی که در حال همکاری هستید، اشتباه کردن کار راحتی نیست. اما منبع باز همه چیز در مورد همکاری و کار با هم است. ما می خواستیم روشی را که مشارکت کنندگان منبع باز جدید یاد می گیرند و برای اولین بار مشارکت می دهند، ساده کنیم.
خواندن مقاله‌ها و دیدن ویدئوهای آموزشی کمک کننده است، ولی چه چیزی بهتر از این است که واقعاً کارها را بدون خراب کردن چیزی انجام دهید. هدف این پروژه ارائه راهنمایی و ساده‌سازی روشی است که تازه‌کاران اولین مشارکت خود را انجام می‌دهند. به یاد داشته باشید که هر چه آرامش بیشتری داشته باشید بهتر یاد می گیرید. اگر به دنبال اولین مشارکت خود هستید، فقط مراحل ساده زیر را دنبال کنید. ما به شما قول می دهیم، سرگرم کننده خواهد بود.
اگر برنامه `GitHub Desktop` رو نصب نداری، [از اینجا نصب کن](https://desktop.github.com/).
اگر از نسخه `GitHub Desktop` قبل از 1.0 استفاده می کنید،[به این آموزش مراجعه کنید](github-desktop-old-version-tutorial.md).
<img align="right" width="255" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## مخزن را فورک کنید
با کلیک کردن بر روی دکمه Fork، از مخزن مورد نظر یک انشعاب بگیرید.
این عملیات یک نسخه کپی از مخزن را بر روی حساب کاربری شما ایجاد می‌کند.
## مخزن را کلون (شبیه) کنید
اکنون این مخزن را در دستگاه خود کلون کنید.
مهم: مخزن اصلی را کلون نکنید. به فورک خود بروید و آن را شبیه سازی کنید.
برای کلون کردن مخزن، روی "Clone or Download" کلیک کنید و سپس روی "Open in Desktop" کلیک کنید.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
یک پنجره پاپ آپ باز می شود. بر روی "Open GitHubDesktop.exe" کلیک کنید.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
پس از کلیک بر روی "Open GitHubDesktop.exe" محتویات در کامپیوتر شما دانلود می شود.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
اکنون محتویات مخزن `first-contributions` در github را در کامپیوتر خود کپی کرده اید.
## یک شاخه جدید ایجاد کنید
اکنون با کلیک بر روی نماد "Current branch" در بالا و سپس روی "New branch" یک شاخه ایجاد کنید:
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="make a branch" />
نام شاخه خود را بگذارید. به عنوان مثال، "add-john-hazrati"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
روی `Create branch` کلیک کنید.
## تغییرات را اعمال کنید و کامیت کنید
حالا به تب history رفته و فایل `Contributors.md` را در یک ویرایشگر متن با کلیک راست و باز کردن در ویرایشگر متن باز کنید. به پایین صفحه بروید و نام خود را به آن اضافه کنید، سپس فایل را ذخیره کنید.
مثال: اگر نام شما جان حضرتی است، باید به این شکل باشد.
\[John Hazrati](https://github.com/john-6670)
می بینید که تغییراتی در Contributors.md وجود دارد و آنها به Github Desktop اضافه شده اند.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
اکنون آن تغییرات را کامیت کنید:
در قسمت _summary_ پیام "Add `<Your-name>` to Contributors list" را بنویسید.
بخش `<Your-name>` را با نام خود جایگزین کنید.
روی دکمه ای که می گوید `Commit to add-your-name` کلیک کنید.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
در پایین مشاهده می کنید که commit ایجاد شده است.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit your changes" />
## تغییرات را ارسال (پوش) کنید
روی File-> Options کلیک کنید و وارد Github.com شوید. نام کاربری و رمز عبور Github خود را وارد کنید.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in to Github" />
روی دکمه `Publish` در بالا سمت راست کلیک کنید.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push your changes" />
## تغییرات خود را برای بررسی، ثبت کنید
اگر به مخزن خود در github بروید، دکمه `Compare & pull request` را خواهید دید. روی آن دکمه کلیک کنید
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
اکنون pull request را ارسال کنید.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
به زودی تمام تغییرات شما را در شاخه اصلی این پروژه ادغام خواهم کرد. پس از ادغام تغییرات، یک ایمیل اعلان دریافت خواهید کرد.
## اقدامات بعدی
تبریک میگم شما به تازگی چرخه استاندارد _fork -> clone -> edit -> PR_ ا را تکمیل کرده اید که اغلب به عنوان یک مشارکت کننده با آن مواجه می شوید!
مشارکت خود روی این پروژه را [از اینجا](https://firstcontributions.github.io#social-share) با دیگر دوستان و دنبال‌کنندگان خود جشن بگیرید.
همچنین شما می‌توانید [از اینجا](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FAA)، وارد تیم Slack ما شوید و سوالات خود را مطرح نمایید.
### [اطلاعات بیشتر](../additional-material/git_workflow_scenarios/additional-material.md)
## آموزش انجام مشارکت در دیگر ابزارها
[برگشت به صفحه اصلی](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Portuguese/github-desktop-tutorial.pt_br.md
+118
View File
@@ -0,0 +1,118 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
É difícil. É sempre difícil fazer algo pela primeira vez. Especialmente quando se está colaborando, cometer erros não é algo agradável. Mas _open source_ (código aberto) se trata de colaboração e de trabalharmos juntos. Queremos simplificar a forma com que novos colaboradores _open source_ aprendem e contribuem pela primeira vez.
Ler artigos e ver tutoriais pode ajudar, mas o que é melhor do que realmente pôr a mão na massa em um ambiente prático? Este projeto visa guiar e simplificar a forma com que os novatos fazem a sua primeira contribuição. Se quiser fazer a sua primeira contribuição, siga os passos abaixo.
Se você nao tem o Github desktop na sua máquina, [instale aqui](https://desktop.github.com/).
Se você está usando uma versão do Github desktop antes da 1.0, [consulte este tutorial](github-desktop-old-version-tutorial.md).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork este repositório" />
## Fork este repositório
Fork este repositório clicando no botão fork na parte superior direita dessa página.
Isso vai criar uma cópia desse repositório na sua conta.
## Clone este repositório
Agora clone esse repositório na sua máquina.
IMPORTANTE: NÃO CLONE O REPOSITÓRIO ORIGINAL. Vá para o seu fork e clone.
Para clonar esse repositório, clique em "Clone or Download" e então clique em "Open in Desktop".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone este repositório" />
Uma janela pop up vai aparecer. Clique em "Open GitHubDesktop.exe".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone este repositório" />
Depois de clicar em "Open GitHubDesktop.exe" os arquivos serão baixados para o seu computador.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone este repositório" />
Agora você copiou os arquivos do repositório first-contributions no github para o seu computador.
## Criando uma branch (ramo)
Agora crie uma branch clicando na aba "Current branch" que fica no topo, depois clique em "New branch":
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="criar uma branch" />
Nomeie sua branch como <add-your-name>. Por exemplo, "add-james-smith"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="nomeie sua branch" />
Clique em `Create branch`
## Faça as mudanças necessárias e commit essas mudanças
Agora abra o arquivo `Contributors.md` em um editor de texto, vá para o final do arquivo e adicione seu nome, depois salve o arquivo.
Exemplo: Se o seu nome for James Smith, Deve ficar parecido com isso.
\[James Smith](https://github.com/jamessmith)
Você pode ver as alterações feitas em Contributors.md no Github Desktop.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="checar mudanças" />
Agora faça commit dessas alterações:
Escreva a mensagem "Add `<your-name>` to Contributors list" no campo _sumary_
Substitua `<your-name>` pelo seu nome.
Clique no botão que diz `Commit to add-your-name`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit suas alterações" />
Na parte inferior, você pode ver que o commit foi criado com sucesso.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit suas alterações" />
## Faça o push das mudanças no github
Clique em File -> Options e depois em sign-in to Github.com. Digite seu username e senha do Github.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in no Github" />
Clique no botão `Publish` na parte superior direita.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push suas alterações" />
## Envie suas alterações para review
Se você for até seu repositório no github, verá o botão `Compare & pull request`. Clique nesse botão
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="criando um pull request" />
Agora envie o pull request.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="enviando o pull request" />
Em breve estarei mesclando todas as suas alterações na branch Master do projeto. Você vai receber um email de notificação assim que as alterações forem integradas.
## Qual o próximo passo?
Parabéns! Você acabou de completar o fluxo _fork -> clone -> edit -> PR_ que encontrará diversas vezes como contribuidor!
Comemore sua contribuição e compartilhe com seus amigos e seguidores acessando o [web app](https://firstcontributions.github.io#social-share).
Você pode entrar na nossa equipe no Slack caso precise de alguma ajuda ou tenha alguma dúvida. [Entre no Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material adicional](../additional-material/git_workflow_senarios/additional-material.md)
## Tutoriais usando outras ferramentas
[Voltar a página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Portuguese/github-windows-intellij-tutorial.pt_br.md
+126
View File
@@ -0,0 +1,126 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/assets/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
| <img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/9/9c/IntelliJ_IDEA_Icon.svg" width="40"> | IntelliJ IDEA |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
É difícil, sempre é difícil quando fazemos alguma coisa pela primeira vez. Especialmente quando você está colaborando, cometendo erros, não é nada confortável. No entanto, o open source é totalmente sobre colaboração & trabalho em equipe. Por isso, nós queremos simplificar a maneira como os novos colaboradores de código aberto aprendem & contribuem pela primeira vez.
Ler artigos & assistir a tutoriais até podem ajudar, mas o que é melhor do que fazer as coisas sem bagunçar nada. Este projeto tem como objetivo orientar & simplificar a forma como os iniciantes fazem a sua primeira contribuição. Lembre-se que você aprende melhor quando está relaxado. Se você deseja fazer sua primeira contribuição, basta seguir os passos abaixo. Nós prometemos a você que será divertido!
Se você ainda não tem o IntelliJ IDEA no seu computador, [instale-o](https://www.jetbrains.com/idea/download/#section=windows)
**Observação:** Este tutorial foi feito usando o IntelliJ IDEA (versão 2019.3.2) em um computador rodando Windows 10. Posteriormente neste tutorial, faremos uso de algumas teclas de atalho, que podem ser diferentes em outros sistemas operacionais (macOS / Linux).
## Faça o Fork deste repositório
<img align="right" width="300" src="https://camo.githubusercontent.com/fcf9a4ed664cc63de2fcb14d1135072ba6d4c74a8e9bdb224ad6ab1e72600c3b/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f666f726b2e706e67" alt="fork this repository" />
Faça um *fork* deste repositório clicando no botão *fork* (bifurcar) no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub.
O GitHub rastreia a relação entre seu repositório e o original, o qual você fez o *fork*. Você pode pensar em seu repositório como uma cópia de trabalho.
Muitos dos repositórios matrizes do GitHub (ou seja, aqueles que não são *Fork* de nenhum outro repositório) tem um pequeno grupo de pessoas que podem fazer commits de modificações diretamente. Todos os outros contribuidores devem fazer um *for* do repositório e fazer alterações no *fork*, em seguida, devem criar um Pull Request para solicitar um *Merge* (mesclagem) das modificações feitas no repositório original.
## Clone seu Repositório
<img align="right" width="300" src="https://camo.githubusercontent.com/4c3f7f1bec4f04db40ecf58dc2e19c2d8992f100f3bbbc4767a9d20b29f4a43d/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f636c6f6e652e706e67" alt="clone this repository" />
O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard".
**CUIDADO**: Um erro que os novatos costumam cometer é clonar o repo do qual você fez o fork, em vez de clonar seu repo. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório.
Agora abra o IntelliJ IDEA.
O IntelliJ IDEA permite que você fassa um check out (em termos do Git clone) de um repositório existente e crie um novo projeto com base nos dados que você baixou.
No menu principal, escolha VCS | Get from Version Control ou, se nenhum projeto estiver aberto no momento, clique em Get from Version Control na tela inicial.
Na caixa de diálogo Get from Version Control dialog, especifique a URL do repositório remoto que deseja clonar (você pode clicar em Test para certificar-se de que a conexão com o repositório remoto pode ser estabelecida) ou selecione um dos serviços de hospedagem VCS à esquerda. Se você já estiver conectado ao serviço de hospedagem selecionado, a completion irá sugerir a lista de repositórios disponíveis que você pode clonar.
Clique em Clone. Se quiser criar um projeto IntelliJ IDEA com base nas fontes que você clonou, clique em Sim na caixa de diálogo de confirmação. O mapeamento de raiz do Git será automaticamente definido para o diretório raiz do projeto.
Se o seu projeto tiver submodelos, eles também serão clonados e automaticamente registrados como raízes do projeto.
**Importante**: certifique-se de que é o repositório é o fork e não o original, caso contrário, o procedimento não funcionará.
## Crie um branch
No Git, o processo de branching (ramificação) é um mecanismo poderoso que permite divergir da linha principal de desenvolvimento, por exemplo, quando você precisa trabalhar em um recurso ou congelar um determinado estado de uma base de código para um release e assim por diante.
No IntelliJ IDEA, todas as operações com branches são realizadas no pop-up Git Branches. Para ativá-lo, clique no widget Git na barra de status ou pressione Ctrl + Shift + `.
O nome do branch atual é exibido no widget do Git na barra de status.
No pop-up branch, escolha Novo branch.
Na caixa de diálogo que é aberta, especifique o nome do branch e certifique-se de que a opção Checkout branch esteja selecionada se você quiser alternar para esse branch.
A nova ramificação começará a partir do HEAD atual. Se você deseja iniciar um branch de um commit anterior ao invés do branch atual HEAD, selecione este commit na aba Log da janela da ferramenta de Controle de Versão Alt + 9 e escolha New Branch no menu de contexto.
## Faça as alterações necessárias
Abra ``Contributors.md`` e adicione seu nome em qualquer lugar do arquivo. Este arquivo contém GFM (GitHub Flavored Markdown), que é um tipo proprietário da sintaxe de [markdown](https://pt.wikipedia.org/wiki/Markdown).
Copie uma das linhas de outros contribuidores e modifique-a com seu nome para ter certeza que você obteve a sintaxe correta.
## Commit & Push modificações para o GitHub
Selecione os arquivos que deseja commitar ou uma lista de alterações inteira na guia Local Changes da janela da ferramenta de controle de versão Alt + 9 e pressione Ctrl + K ou clique no botão Commit na barra de ferramentas.
A caixa de diálogo Commit Changes abrira e listara todos os arquivos que foram modificados desde o último commit, bem como todos os arquivos não versionados recém-adicionados.
Insira uma mensagem de commit que faça sentido.
Você pode clicar em Commit Message history (Confirmar histórico de mensagens) Ctrl + M para escolher na lista de mensagens de commits recentes.
Você também pode editar a mensagem de commit mais tarde, antes de enviar o commit.
Pressione Ctrl + Shift + K ou escolha VCS | Git | Push from the main menu. A caixa de diálogo Push Commits é aberta, mostrando todos os repositórios Git (para projetos de vários repositórios) e listando todos os commits feitos no branch atual em cada repositório desde o último push.
## Envie suas alterações para revisão
Neste ponto, você concluiu a alteração, mas ela ainda está apenas no seu repo. Esta etapa mostrará como enviar uma solicitação ao administrador do repo matriz para mesclar sua alteração.
Em seu repo no GitHub, você verá o botão `Compare & pull request` ao lado da notificação do novo branch, clique nesse botão.
<img src="https://camo.githubusercontent.com/ca3b1cefece5f3b9b3435020e6a357ca024cda5bd2b1e140a15170fcd1ec5381/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f636f6d706172652d616e642d70756c6c2e706e67" alt="create a pull request" />
Agora submeta o pull request.
<img src="https://camo.githubusercontent.com/71401ba5551a64aeac3838825a52ce7a7597cd8b54a0d7200d9454e2cbfbb13f/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f7375626d69742d70756c6c2d726571756573742e706e67" alt="submit pull request" />
Em breve estarei mesclando todas as suas alterações no branch master deste projeto. Você receberá um e-mail de notificação assim que as alterações forem integradas.
## Para onde ir agora?
Parabéns! Você acabou de completar o padrão _fork -> clone -> edit -> PR_ workflow que você encontrará frequentemente como um contribuidor!
Comemore sua contribuição e compartilhe-a com seus amigos e seguidores acessando o [web app](https://firstcontributions.github.io/#social-share).
Você pode se juntar a nossa equipe slack caso precise de alguma ajuda ou tenha alguma dúvida. [Junte-se ao time slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
Agora vamos começar a contribuir para outros projetos, compilamos uma lista de projetos com questões fáceis para você começar. [Confira a lista de projetos no web app](https://firstcontributions.github.io/#project-list).
### [Material Adicional](../../additional-material/translations/Portuguese/additional-material.pt_br.md).
## Tutoriais usando outras ferramentas
[Voltar a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md)
## Autopromoção
Se você gostou deste projeto, de star no GitHub. Se você gostou dessa tradução me siga no GitHub [Vitor Matias](https://github.com/VitorCMatias).
docs/gui-tool-tutorials/translations/Portuguese/github-windows-vs-code-tutorial.pt_br.md
+117
View File
@@ -0,0 +1,117 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
É difícil. É sempre difícil a primeira vez que você faz algo. Especialmente quando você está colaborando, cometer erros não é uma coisa confortável. Mas o código aberto tem tudo a ver com colaboração e trabalho em conjunto. Queríamos simplificar a maneira como os novos colaboradores de código aberto aprendem e contribuem pela primeira vez.
Ler artigos e assistir a tutoriais pode ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada. Este projeto visa fornecer orientação e simplificar a maneira como os novatos fazem sua primeira contribuição. Lembre-se, quanto mais relaxado você estiver, melhor você aprenderá. Se você está procurando fazer sua primeira contribuição, basta seguir os passos simples abaixo. Nós prometemos a você, vai ser divertido.
Se você não tiver o Visual Studio Code em sua máquina, [instale-o](https://code.visualstudio.com/download).
**Atenção:** Este tutorial foi feito usando o Visual Studio Code (Versão 1.27.2) em uma máquina Windows 10. Mais adiante neste tutorial, usaremos alguns atalhos de teclado. Eles podem diferir em outros sistemas operacionais (macOS/Linux), bem como no idioma do teclado (UK, DE, etc). Você pode percorrer sua lista de atalhos pesquisando "atalho" na Paleta de Comandos.
## Fork este repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Fork este repositório clicando no botão fork no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub.
O GitHub acompanha o relacionamento entre seu repositório e aquele do qual você o bifurcou. Você pode pensar em seu repositório como uma cópia de trabalho.
A maioria dos repositórios de alto nível do GitHub (ou seja, aqueles que não são bifurcados de nenhum outro repositório) têm uma pequena equipe principal de pessoas que podem confirmar alterações diretamente. Todos os outros contribuidores devem bifurcar o repositório e fazer alterações na bifurcação e, em seguida, criar uma solicitação de pull para solicitar que suas alterações sejam mescladas novamente no repositório de nível superior. Se o administrador de repo de nível superior gostar das alterações, elas serão mescladas e você ganhará fama e fortuna instantâneas! Mais sobre como fazer isso mais tarde.
## Clone seu repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
A próxima etapa é clonar seu repositório para sua máquina para que você possa começar a fazer alterações. O VS Code precisa do URL do seu repositório, então clique no botão "clone" e depois clique no ícone "copiar para a área de transferência".
**CUIDADO:** Um erro que os novos contribuidores costumam cometer é clonar o repositório que você bifurcou _de_ em vez de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de estar clonando seu repositório.
Agora abra o Visual Studio Code. A página de boas-vindas do VS Code aparecerá. A partir daí, pressione `F1` para abrir a barra mostrada abaixo. Observe que já existe um sinal `>` (maior que) no campo de texto. Você também pode acessar o prompt de entrada pressionando `CTRL-P` e digite o caractere `>`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Você pode notar que já existem alguns comandos obscuros listados abaixo. Esses são meus comandos usados recentemente. Então, simplesmente não se importe com eles.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Agora digite `git clone`, apenas `git` ou `clone` (funciona como uma pesquisa).
Selecione a entrada `Git: Clone` e pressione `Entrar`
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Colar URL do repositório" />
Cole a URL do seu repositório e pressione `Entrar`. Isso abrirá um File Explorer onde você pode escolher onde o repositório Git deve ser armazenado.
**Importante**: Certifique-se de que é o repositório bifurcado e não o original, caso contrário não funcionará.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Você deve ver um pop-up de status no canto inferior direito do Visual Studio Code. Depois de terminar, você pode abrir o repositório clonado (agora uma pasta em sua máquina) usando os botões da caixa de diálogo.
## Criar uma branch
Abra a paleta de comandos novamente pressionando `F1`. Digite `branch` e selecione o comando `criar branch` a partir daí. Na próxima etapa digite o nome do seu novo branch, por exemplo `add-david-kroell`. Pressione enter e a ramificação será criada. A filial também já foi verificada. [O que significa checkout?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Faça as alterações necessárias
Abra `Contributors.md` e adicione seu nome em qualquer lugar do arquivo. Este arquivo contém GFM (GitHub Flavored Markdown), que é um sabor proprietário da sintaxe <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Copie um dos outros contribuidores&apos; linhas e modifique-o com seu nome para ter certeza de obter a sintaxe correta - pode ser exigente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Confirmar e enviar alterações para o GitHub
No lado esquerdo do VS Code há um menu com 5 ícones exibidos. Selecione o ícone de controle de versão/Controle de origem.
(Atalho: Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commitar alterações" />
O explorador de arquivos exibe todos os arquivos que foram alterados após o último commit. Ao passar o mouse sobre os arquivos e clicar em `+` (mais), os arquivos são encenados.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Arquivos guardados">
Digite algo na linha na parte superior do explorer e pressione a marca de seleção. As alterações agora estão confirmadas em sua cópia local. Agora as alterações precisam ser enviadas de volta ao GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Arquivos guardados">
Use o ícone de três pontos para abrir o menu onde você seleciona a opção `Publicar Branch`. Isso deve abrir uma caixa de diálogo para colocar suas credenciais do GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Arquivos guardados">
## Envie suas alterações para revisão
Neste ponto, você concluiu sua alteração, mas ela ainda reside apenas em seu repositório. Esta etapa mostrará como enviar uma solicitação ao administrador do repositório de nível superior para mesclar sua alteração.
Em seu repositório no GitHub, você verá o botão `Comparar & pull request` ao lado da nova notificação de branch. Clique nesse botão.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="crie uma pull request" />
Agora envie a solicitação PR - pull request.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Em breve estarei mesclando todas as suas alterações no branch master deste projeto. Você receberá um e-mail de notificação assim que as alterações forem mescladas.
## Para onde ir a partir daqui?
Parabéns! Você acabou de concluir o fluxo de trabalho padrão _fork -> clone -> editar -> PR_ que você encontrará frequentemente como colaborador!
Comemore sua contribuição e compartilhe com seus amigos e seguidores acessando [aplicativo da web](https://firstcontributions.github.io#social-share).
Você pode se juntar à nossa equipe do slack caso precise de ajuda ou tenha alguma dúvida. [Junte-se à equipe do Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material adicional](../additional-material/translations/additional-material.pt_br.md)
## Tutoriais usando outras ferramentas
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Portuguese/github-windows-vs-code-tutorial_pt_br.md
+124
View File
@@ -0,0 +1,124 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
É difícil, sempre é difícil quando fazemos alguma coisa pela primeira vez. Especialmente quando você está colaborando, cometendo erros, não é nada confortável. No entanto, o open source é totalmente sobre colaboração e trabalho em equipe. Por isso, nós queremos simplificar a maneira como os novos colaboradores de código aberto aprendem e contribuem pela primeira vez.
Ler artigos e assistir a tutoriais até podem ajudar, mas o que é melhor do que fazer as coisas sem bagunçar nada. Este projeto tem como objetivo orientar & simplificar a forma como os iniciantes fazem a sua primeira contribuição. Lembre-se que você aprende melhor quando está relaxado. Se você deseja fazer sua primeira contribuição, basta seguir os passos abaixo. Nós prometemos a você que será divertido!
Se você não tem o Visual Studio 2017 na sua máquina, [instale-o](https://code.visualstudio.com/download).
**Nota:** Este tutorial foi feito utilizando o Visual Studio Code (Versão 1.27.2) no Windows 10. Mais tarde, neste tutorial, vamos utilizar alguns atalhos no teclado. Eles podem ser diferentes em outros sistemas operacionais (mac/OS/Linux) assim como em teclados de outras linguagens (UK, DE, etc). Você pode pesquisar na lista de atalhos, buscando por "atalhos" na Paleta de Comando.
## Faça o *Fork* deste repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Faça um *fork* deste repositório clicando no botão *fork* (bifurcar) no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub.
O GitHub rastreia a relação entre seu repositório e o original, o qual você fez o *fork*. Você pode pensar em seu repositório como uma cópia de trabalho.
Muitos dos repositórios matrizes do GitHub (ou seja, aqueles que não são *Fork* de nenhum outro repositório) tem um pequeno grupo de pessoas que podem fazer commits de modificações diretamente. Todos os outros contribuidores devem fazer um *fork* do repositório e fazer alterações no *fork*, em seguida, devem criar um Pull Request para solicitar um *Merge* (mesclagem) das modificações feitas no repositório original.
Se um dos administradores do repositório gostar e aprovar as tuas mudanças, eles *mergearão* e você ganhará fama e fortuna imediatamente! Abaixo, há mais detalhes sobre como fazer isso.
## Clone o seu repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard".
**CUIDADO:** Um erro que os novatos cometem com frequência é clonar o repositório do qual você fez o fork, ao invés de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório.
Agora, abra o Visual Studio Code. A página principal do VS Code vai minimizar. A partir daí, pressione `F1` para abrir a barra mostrada abaixo. Perceba que já existe um `>` (maior que) no campo de texto. Você pode também chegar até o prompt de entrada pressionando `CTRL-P` e então inserindo o caracter `>`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Você pode notar que já aí já existem alguns comandos de sugestão abaixo. Esses são os seus comandos utilizados recentemente. Então, apenas ignore-os.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Agora, digite `git clone`, apenas `git` ou `clone` (isso funcionará como uma pesquisa).
Selecione a opção `Git: Clone` e então aperte `Enter`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
Cole a URL do seu repositório e aperte `Enter`. Isso vai abrir o Explorador de Arquivo onde você pode escolher onde o repositório Git será armazenado.
**Importante**: Tenha certerza que este é o repositório *forkeado* e não é o original. Se não, não funcionará.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Você pode ver uma janela do status no canto inferior direito do Visual Studio Code. Depois de finalizado esse processo, você pode abrir o repositório clonado (agora, uma pasta na sua máquina) e usar os botões no diálogo.
## Crie uma *branch*
Abra a Paleta de Comando novamente, pressionando `F1`. Digite nele `branch` e selecione o comando `create branch` a partir das sugestões. No próximo passo, digite o nome da sua nova *branch*, por exemplo: `add-david-kroell`. Presione `Enter` e a *branch* será criada. A *branch* também está preparada para o *check out*. [*O que isso significa?*](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Faça as mudanças necessárias
Abra o arquivo `Contributors.md` e adicione o seu nome no fim da lista. Esse arquivo contém GFM (GitHub Flavored Markdown), que é uma função nativa da sintaxe do <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Copie uma das outras linhas dos contribuidores e modifique-a com o seu nome. Tenha certeza que a sintaxe está correta - ela pode ser exigente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Faça um *Commit* & um *Push* das suas mudanças para o GitHub
No lado esquerdo do VS Code tem um menu com 5 ícones a amostra. Selecione o ícone de `Controle de Versão/Controle da Fonte`.
(Atalho : Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
O Explorador de arquivos mostra todos os arquivos que foram mudados depois do último commit. Sobrepondo o mouse nos arquivos e clicando no `+` (mais) os arquivos serão colocados no *stage*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
Escreva algo na caixa de texto, no topo do explorador e pressione o botão de *check*. As mudanças agora foram *commitadas* para a sua cópia local. Agora, as mudanças tem que serem mandadas para o GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
Use o ícone dos três pontos para abrir o menu onde você selecionará a opção `Publicar Branch`. Isso deve abrir uma caixa de diálogo para colocar as tuas credenciais do GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## Submeta suas mudanças para uma revisão
Nesse ponto, você completou suas mudanças, mas elas ainda estão no seu repositório. Esse passo vai mostrar para você como submeter uma requisição para o administrador do repositório original para *mergear* suas mudanças.
No seu repositório no GitHub você verá o botão `Compare & Pull request` próximo a notificação da branch. Clique nesse botão.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Agora, submeta o *pull request*.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Breve as suas mudanças serão *mergeadas* na branch `master` desse projeto. Você será notificado por email uma vez que as mudanças forem *mergeadas*.
## Para onde ir ?
Parabéns! Você acabou de completar o fluxo de trabalho *fork -> clone -> edit -> PR* que vocẽ vai realizar frequentemente como um contribuidor!
Celebre a sua contribuição e compartilhe-a com os seus amigos e seguidores indo para o [web app](https://firstcontributions.github.io#social-share).
Você pode se juntar à nossa comunidade no slack, caso precise de alguma ajuda ou tenha alguma dúvida.
[Faça parte da nossa comunidade no Slack!](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY)
### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriais utilizando outras ferramentas
[Retorne para a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md)
docs/gui-tool-tutorials/translations/Portuguese/github-windows-vs2017-tutorial.pt_br.md
+149
View File
@@ -0,0 +1,149 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
|<img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/61/Visual_Studio_2017_logo_and_wordmark.svg/2000px-Visual_Studio_2017_logo_and_wordmark.svg.png" width="200">|Visual Studio 2017 Edition|
|---|---|
É difícil. Sempre é difícil fazer algo pela primeira vez. Especialmente quando você está colaborando, cometer erros não é confortável. Mas o open sourece tem tudo a ver com colaboração e trabalho em equipe. Nós queremos simplificar a maneira de aprendizagem aos novos contribuidores de open source e ajudar em sua primeira contribuição.
Lendo artigos e olhando tutoriais podem ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada.
Esse projeto visa em providenciar uma orientação e simplificar a maneira dos novatos a conseguirem a sua primeira contribuição.
Lembre-se, quanto mais relaxado melhor será o aprendizado. Se você está procurando em fazer a sua primeira contribuição, siga esses passos abaixo. Nós prometemos a você que vai ser divertido.
Se você não possui o Visual Studio 2017 na sua máquina, [instale-o aqui](https://www.visualstudio.com/downloads/).
## Faça um Fork deste repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/fork.png" alt="fork this repository" />
Para fazer um Fork deste repositório, basta clicar no botão de fork no topo da página. Isso criará uma cópia do repositório na
sua conta GitHub.
O GitHub acompapanhará o seu Fork e o repositório principal. Em outras palavras, podemos afirmar que o seu Fork é uma cópia do repositório principal.
Os respositórios de mais alto nível do GitHub (exemplo: aqueles que não há um fork de nenhum outro repositório), tem uma pequena equipe principal de pessoas que podem diretamente fazer os seus commits. Os outros contribuidores deverão criar um Fork do respositório e fazer as mudanças nesse Fork, em seguida criar um Pull Request perguntando se essas mudanças poderão ser mescladas no repositório de alto nível. Se o administrador do repositório gostar das alterações ele irá mesclar as modificações e você ganhará instantaneamente fama e fortuna! Abaixo há um tutorial de como realizar.
## Clone o seu repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/clone.png" alt="clone this repository" />
O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard".
**CUIDADO:** Um erro que os novatos cometem com frequência é clonar o repositório do qual você fez o fork, ao invés de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório.
Agora é a hora de ir para o Visual Studio 2017! Você estará trabalhando na aba *Team Explorer* na maior parte do tutorial. Se ela não estiver aberta por padrão, clique em `View > Team Explorer` para abrí-la.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-01-clone1.png" alt="Team Explorer" />
*Team Explorer* tem muitas áreas e muitos botões de navegação, localizados no topo para te ajudar a achar essas diferentes áreas. Para clonar o repositório, você vai precisar estar na *Connect view*, que deve ser a padrão. Se você não conseguir ver o botão *clone*, clique no botão verde, em formato de tomada, no topo.
Click the `Clone` option under **Local Git Repositories** and paste the URL to your repo in the text box. This should be the URL you copied to your clipboard from GitHub previously.
Clique na opção `Clone` abaixo de **Local Git Repositories** e cole a URL do seu repositório na caixa de texto. Essa URL tem que ser a mesma que você copiou no GitHub anteriormente.
Clique no botão `Clone` para iniciar o processo.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-02-clone2.png" alt="Clone repo" />
Quando o processo estiver completo, você será movido para a aba *Solution Explorer*, onde você poderá ver o conteúdo do repositório clonado. O seu parecerá um pouco diferente da foto abaixo, por que os arquivos estão em constante mudança!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-03-clone3.png" alt="Solution Explorer" />
## Crie uma *branch*
Clique de volta na aba *Team Explorer* e use o a seleção principal de navegação para mostrar as *Branchs* disponíveis.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-04-branch1.png" alt="Branches view" />
Você deve ver o repositório **first-contributions** e a branch padrão, que é chamada `main`. Clique com o botão direito na `main` e escolha `New Local Branch From...`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-05-branch2.png" alt="New branch" />
Dê à sua branch um nome como `add-<seu_nome_aqui>` por exemplo: `add-alonzo-church`.
Deixe a caixa de seleção `Checkout branch` marcada e clique no botão `Create Branch`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-06-branch3.png" alt="Create branch" />
Você deverá ver a sua branch nova na lista.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-07-branch4.png" alt="See new branch" />
## Faça as mudanças necessárias
Abra o arquivo `Contributors.md` e adicione o seu nome no fim da lista. Esse arquivo contém GFM (GitHub Flavored Markdown), que é uma função nativa da sintaxe do <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Copie uma das outras linhas dos contribuidores e modifique-a com o seu nome. Tenha certeza que a sintaxe está correta - ela pode ser exigente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-08-change1.png" alt="Add your name" />
## Commit & Push changes to GitHub
Volte para a aba *Team Explorer* e navegue para a aba *Changes*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-09-commit1.png" alt="Changes" />
Coloque a informação que você queira, poste o seu *commit* e clique em `Save`. O Visual Studio relembrará isso para futuros *commits*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-10-commit2.png" alt="Git user information" />
**NOTA:** Visual Studio usa uma pasta escondida, chamada `.vs` para salvar suas configurações e preferências pessoais. O conteúdo desta pasta **não deverá ser salvo no Git**.
Se ela não estiver sido ingnorada ainda, você deve informar ao Git para ignorar essa pasta, com o intuito dela não ser mandada para o repositório.
Essa pasta já foi ignorada neste repositório, então você não tem que realizar este passo. Ele está aqui somente para você ter uma referência para projetos futuros.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-11-commit3.png" alt="Ignore vs folder" />
Agora você deve ver uma lista de arquivos modificados e uma caixa de texto para digitar um cometário do *commit*. Os comentários devem ser breves, mas concretos. Não tem nada pior do que ler um comentário de um *commit* e ver algo como: `"Eu atualizei algumas coisas"`. Tire alguns segundos para realizar o seu *commit*. O seu time vai agradecer bastante mais tarde e você pode até agradecer a você mesmo!
Clique em `Commit All and Push` para realizar um *commit* local e fazer um *push* das suas mudanças para o seu repositório, tudo em um único passo.
**NOTA:** Um *Commit* pode ser realizado separadamente de um *Push*. Fazemos os dois juntos por conveniência. As mudanças realizadas e salvas em *commits* locais não serão refletidos no teu repositório no GitHub até que você faça um *Push*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-12-commit4.png" alt="Commit and Push" />
A primeira vez que você realizar um *Push* para o GitHub, Visual Studio solicitará as suas credenciais do GitHub. Depois disso, ele as guardará no *cache*, para que você não precise realizar isso frequentemente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-13-commit5.png" alt="Login" />
Depois de realizar uma operação de *Push*, abra o seu repositório no GitHub e deverá ver uma mensagem indicando um *push* recente de uma *branch*.
Você pode ver suas mudanças abrindo a seleção `Branch: main` e selecionando a sua `branch`. Parabéns! Você pode compartilhar a URL da `branch` com o mundo e mostrar o seu progresso!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-14-commit6.png" alt="View pushed branch on GitHub" />
## Submeta as suas mudanças para uma revisão
Neste ponto, você completou as mudanças, mas elas ainda estão somente no seu repositório. Esse passo te mostrará como submeter essas mudanças para um administrador para que ele possa fazer um *merge* das tuas mudanças.
No seu repositório no GitHub, você verá o botão `Compare & pull request` próximo à notificação da *branch*. Cloque nesse botão.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/compare-and-pull.png" alt="create a pull request" />
Agora submeta o *Pull Request*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/submit-pull-request.png" alt="submit pull request" />
Assim que possível, essas mudanças serão *mergeadas* para a `main branch` deste projeto. Você será notificado via email, quando essa movimentação for realizada.
## Para onde ir daqui?
Parabéns! Você acabou de completar o fluxo de trabalho *fork -> clone -> edit -> PR* que vocẽ vai realizar frequentemente como um contribuidor!
Celebre a sua contribuição e compartilhe-a com os seus amigos e seguidores indo para o [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).
Você pode se juntar à nossa comunidade no slack, caso precise de alguma ajuda ou tenha alguma dúvida.
[Faça parte da nossa comunidade no Slack!](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY)
### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriais utilizando outras ferramentas
[Retorne para a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md)
docs/gui-tool-tutorials/translations/Portuguese/gitkraken-tutorial.pt-br.md
+126
View File
@@ -0,0 +1,126 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
|<img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/61/Visual_Studio_2017_logo_and_wordmark.svg/2000px-Visual_Studio_2017_logo_and_wordmark.svg.png" width="200">|Visual Studio 2017 Edition|
|---|---|
É difícil. Sempre é difícil fazer algo pela primeira vez. Especialmente quando você está colaborando, cometer erros não é confortável. Mas o open sourece tem tudo a ver com colaboração e trabalho em equipe. Nós queremos simplificar a maneira de aprendizagem aos novos contribuidores de open source e ajudar em sua primeira contribuição.
Lendo artigos e olhando tutoriais podem ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada.
Esse projeto visa em providenciar uma orientação e simplificar a maneira dos novatos a conseguirem a sua primeira contribuição.
Lembre-se, quanto mais relaxado melhor será o aprendizado. Se você está procurando em fazer a sua primeira contribuição, siga esses passos abaixo. Nós prometemos a você que vai ser divertido.
## Git Kraken
Baixe [GitKraken](https://www.gitkraken.com), Instale e abra.
Provavelmente aparecerá um "Bem-vindo ao GitKraken" com um espaço para entrar na sua conta do GitHub e permitir que o GitKraken possa ter o acesso dela.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(opcional) Vá para Aqruivos -> Preferências e ajuste o diretório do seu projeto para a raiz de seus repositórios locais.
## Faça um Fork deste repositório
Para fazer um Fork deste repositório, basta clicar no botão de fork no topo da página.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="fork this repository" />
Isso criará uma cópia do repositório na sua conta GitHub.
## Clone o seu repositório
No GitKraken, vá até Arquivo -> Clone Repositório.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
Selecione GitHub.com no painel direito. De baixo do nome de usuário, deverá aparecer "first-contributions". Clique nesse repositório e confirme na parte inferior do painel, se aparece o local do diretório onde você quer clonar.
Quando estiver tudo certo com o diretório, clique em "Clone o repositório!"
## Crie uma Branch
Clique o botão branch na barra de ferramentas.
Nomeie a sua branch "add-seu-nome", for example: "add-william-sutton"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## Faça mudanças necessárias e faça um commit nelas
Agora abra o arquivo `Contributors.md` em um editor de texto e adicione o seu nome, em seguida salve-o.
Se você estiver com o repositório aberto no GitKraken, haverá mudanças.
Revise e faça um Stage nessas mudanças selecionando o commit mais recente marcado com "// WIP" e com número de arquivos modificados e o tipo de mudança.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
Revise esses arquivos que foram modificados e decida o que colocar no Stage. O Stage é importante, pois informa o Git extamente quais arquivos modificados você quer mandar no commit.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
Quando escrever uma boa mensagem no commit ("Add <seu-nome> para a lista de Contribuidores" parece bom e descritivo) e satisfeito com as suas mudanças, você pode apertar no "Stage todas as mudanças" para fazer o Stage em todas as alterações ou "Stage Arquivo" para cada arquivo modificado individualmente.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
Se você mudar de ideia, você pode fazer um Unstage (processo reverso do Stage) das sua modificações ou discartar todas elas juntas.
CUIDADO: A palavra discartar fala por si só, ou seja, é uma operação destrutiva. Só faça isso, se você não quer nenhuma mundança no repositório que estiver trabalhando.
Aperte commit.
Parabéns, você acabou de fazer um commit de todas as suas mudanças na sua branch local do seu Fork. Em diante!
## Faça um Push nas suas modificações para o GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
Na barra de ferramentas, clique no botão Push.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
Se você quer enviar as mudanças direto para branch master, você pode enviar para a branch de origem. Caso contrário, selecione uma branch apropriada para mandar.
## Envie as suas mudanças para revisão
No seu repositório do GitHub você vai ver um botão escrito: `Compare & pull request`, que fica ao lado da notificação da nova branch. Clique nesse botão.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
Agora envie esse Pull Request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit pull request" />
Logo irei mesclar todas as suas mudanças na branch master do projeto. Você receberá uma notificação pelo e-mail quando as alterações forem mescladas.
## Onde eu posso ir a partir daqui?
Parabéns! Você completou o fluxo de trabalho básico _fork -> clone -> edit -> PR_, onde você encontrará muito como contribuidor.
Celebre a sua contribuição e compartilhe com seus amigos e seguidores no [web app](https://firstcontributions.github.io/#social-share).
Caso precise de ajuda ou tenha alguma pergunta, você pode se juntar à nossa equipe Slack. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material Adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriais usando outras ferramentas
[Voltar para página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Spanish/gitkraken-tutorial-es.md
+116
View File
@@ -0,0 +1,116 @@
[![Amor por el Código Abierto](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Licencia: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Ayudantes de Código Abierto](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeras Contribuciones
|<img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="200">|GitKraken Edition|
|---|---|
Es difícil. Siempre es difícil cuando se hace algo por primera vez. Especialmente cuando se colabora, cometer errores no es algo agradable. Pero el código abierto trata sobre la colaboración y el trabajo en conjunto. Queríamos simplificar la manera en que los contribuyentes de código abierto aprenden y contribuyen por primera vez.
Leer artículos y ver tutoriales puede ayudar, pero ¿qué es mejor que hacer las cosas sin estropear nada?. Este proyecto tiene como objetivo proporcionar orientación y simplificar la manera en que los novatos hacen su primera contribución. Recuerda que cuando más relajado estés, mejor aprenderás. Si buscas hacer tu primera contribución sólo sigue los simples pasos a continuación. Te lo prometemos, será divertido.
## Git Kraken
Descarga [GitKraken](https://www.gitkraken.com), Instálalo y ábrelo.
Deberías ver el diálogo modal "Welcome to GitKraken" - Regístrate con Github y permite el acceso a Gitkraken a tu cuenta de GitHub.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(opcional) Dirígete a File -> Preferences y configura el directorio de tu proyecto en la raíz de tus repositorios locales.
## Bifurca (Fork) este repositorio
Bifurca este repositorio clickeando en el botón fork en la parte superior derecha de esta página.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="fork this repository" />
Esto creará una copia de este repositorio en su cuenta.
## Clona el repositorio
En GitKraken, ve a File -> Clone Repo.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
Selecciona GitHub.com en el panel derecho. Bajo tu nombre de usuario, deberías ver first-contributions. Haz click en ese repositorio y verifica la ruta completa mostrada al final del panel.
Una vez estés satisfecho con la ruta, clickea "Clone the repo!".
## Crear una rama (*branch*)
Clickea el botón *branch* de la barra de herramientas.
Nombra tu rama "add-your-name", por ejemplo: "add-william-sutton"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## Haz los cambios necesarios y confirma (*Commit*) esos cambios
Ahora abre el archivo `Contributors.md` en un editor de texto y agrégale tu nombre, luego guarda el archivo.
Si tienes el repositorio abierto en GitKraken deberías ver que hay cambios. Revisa y prepara esos cambios seleccionando la confirmación (*commit*) más reciente marcada con "// WIP" y el número de archivos cambiados y el tipo de cambio.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
Revisa los archivos que han sido cambiados y decide cuáles deseas preparar para confirmar (*stage*). La preparación es importante para decirle a git exactamente que archivos deseas asociar con esta confirmación (*commit*).
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
Una vez tengas un buen mensaje de confirmación (*commit*) ("Add <your-name> to Contributors list" suena agradable y descriptivo) y estés feliz con tus cambios, puedes clickear "Stage all changes" para preparar todo lo modificado o "Stage File" para preparar un archivo individual.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
Si cambias de idea, puedes olvidar (*unstage*) esos cambios, o puedes descartárlos todos.
ADVERTENCIA: Como lo implica la palabra descartar, esta es una operación destructiva. Hazlo solo si no quieres ningún cambio(s) desde cualquier repositorio en el que te encuentres.
Clickea en *commit*.
Felicidades, has confirmado (*committed*) todos los cambios a la copia local de la rama de tu bifurcación (*fork*) de first-contributions.¡Adelante!.
## Sube (*push*) los cambios a GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
Haz click en el botón *Push* en la barra de herramientas.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
Envía los cambios en la rama origen si quieres que los cambios se reflejen en la rama maestra directamente, sino selecciona la rama apropiada a la cual quieres hacer el push.
## Envía tus cambios para revisión
Si vas a tu repositorio en github, verás el botón `Compare & pull request`. Haz click en él.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
Ahora confirma el pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit pull request" />
Pronto estaré fusionando todos sus cambios en la rama master de este proyecto. Recibirás una notificación por correo electrónico cuando los cambios hayan sido fusionados.
## ¿Cuáles son los siguientes pasos?
¡Enhorabuena! ¡Has completado el flujo de trabajo _fork -> clone -> edit -> PR_ que encontrarás habitualmente como contribuidor!
Celebra tu contribución y compártela con tus amigos y seguidores yendo a [App web](https://firstcontributions.github.io/#social-share).
También podrías unirte a nuestro equipo de Slack en caso de que necesites ayuda o tengas alguna pregunta. [Únete a nuestro equipo de Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriales con otras herramientas
[Regresar a la página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/Yoruba/github-desktop-tutorial.ng_yo.md
+104
View File
@@ -0,0 +1,104 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Awọn ẹbun akọkọ
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Ojú-iṣẹ Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
O le. O jẹ lile nigbagbogbo ni igba akọkọ ti o ṣe nkan. Paapa nigbati o ba n ṣe ifowosowopo, ṣiṣe awọn aṣiṣe kii ṣe nkan ti o ni itunu. Ṣugbọn orisun ṣiṣi jẹ gbogbo nipa ifowosowopo & ṣiṣẹ papọ. A fẹ lati jẹ ki o rọrun ni ọna ti awọn oluranlọwọ orisun-ìmọ tuntun kọ ẹkọ & ṣe alabapin fun igba akọkọ.
Awọn nkan kika & wiwo awọn olukọni le ṣe iranlọwọ, ṣugbọn kini o dara julọ ju ṣiṣe nkan naa ni gangan laisi dabaru ohunkohun. Ise agbese yii ni ero lati pese itọnisọna & simplifying ọna ti awọn rookies ṣe ṣe ilowosi akọkọ wọn. Ranti diẹ sii ni ihuwasi ti o dara julọ ti o kọ ẹkọ. Ti o ba n wa ṣiṣe ilowosi akọkọ rẹ kan tẹle awọn igbesẹ ti o rọrun ni isalẹ. A ṣe ileri fun ọ, yoo jẹ igbadun.
Ti o ko ba ni Ojú-iṣẹ GitHub lori ẹrọ rẹ, [fi sii] (https://desktop.github.com/).
Ti o ba n lo ẹya ti tabili GitHub ṣaaju 1.0, [tọkasi ikẹkọ yii](github-desktop-old-version-tutorial.md). <img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt=" orita ibi ipamọ yii" />
## Orita ibi ipamọ yii
Fork repo yii nipa tite lori bọtini orita ni apa ọtun oke ti oju-iwe yii. Eyi yoo ṣẹda ẹda ibi ipamọ yii sinu akọọlẹ rẹ.
## Ti ẹda ibi ipamọ naa
Bayi clone repo yii si ẹrọ rẹ. PATAKI: MAA ṢE TI AWỌN REPO ORIGINAL. Lọ si orita rẹ ki o ṣe oniye rẹ. Lati ṣe oniye repo, tẹ lori "Clone tabi Download" ati lẹhinna tẹ "Ṣii ni Ojú-iṣẹ".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
Ferese agbejade yoo ṣii. Tẹ "Ṣii GitHubDesktop.exe".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
Lẹhin ti o tẹ “Ṣii GitHubDesktop.exe” awọn akoonu naa yoo ṣe igbasilẹ si kọnputa rẹ.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
Bayi o ti daakọ awọn akoonu ti ibi ipamọ awọn ifunni akọkọ ni github si kọnputa rẹ.
## Ṣẹda ẹka kan
Bayi ṣẹda ẹka kan nipa tite lori aami “Ẹka lọwọlọwọ” ni oke ati lẹhinna tẹ “Ẹka Tuntun”:
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
Tẹ 'Ṣẹda ẹka'
## Ṣe awọn ayipada to ṣe pataki ki o ṣe awọn ayipada yẹn
Bayi ṣii faili `Contributors.md` ni olootu ọrọ, yi lọ si isalẹ ti oju-iwe naa ki o fi orukọ rẹ kun, lẹhinna fi faili naa pamọ.
Apeere: Ti orukọ rẹ ba jẹ James Smith, O yẹ ki o dabi eleyi. \[James Smith](https://github.com/jamessmith) O le rii pe awọn ayipada wa si Contributors.md ati pe wọn ti ṣafikun si Ojú-iṣẹ Github.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
Bayi ṣe awọn ayipada wọnyi:
Kọ ifiranṣẹ naa "Ṣafikun `<orukọ-orukọ rẹ>` si atokọ Awọn oluranlọwọ” ni aaye _ akopọ _.
Ropo `<oruko-rẹ>` pẹlu orukọ rẹ.
Tẹ bọtini ti o sọ 'Ṣe lati fi-orukọ-rẹ'.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
Ni isalẹ, o le rii pe a ti ṣẹda ifaramọ naa.
<img style="osi;" src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt = "ṣe awọn ayipada rẹ" />
## Titari awọn ayipada si github
Tẹ Faili-> Awọn aṣayan ati wọle si Github.com. Tẹ orukọ olumulo Github ati ọrọ igbaniwọle sii.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt = "wọle si Github" />
Tẹ bọtini 'Tẹjade' ni apa ọtun oke.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt = "Titari awọn ayipada rẹ" />
## Firanṣẹ awọn ayipada rẹ fun atunyẹwo
Ti o ba lọ si ibi ipamọ rẹ lori github, iwọ yoo rii bọtini 'Afiwe & fa ìbéèrè'. tẹ lori wipe bọtini.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt = "ṣẹda ibeere fifa" />
Bayi fi ibeere fa silẹ.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt = "fi ìbéèrè fa" />
Laipẹ Emi yoo dapọ gbogbo awọn ayipada rẹ si ẹka ọga ti iṣẹ akanṣe yii. Iwọ yoo gba imeeli iwifunni ni kete ti awọn ayipada ba ti dapọ.
## Nibo ni lati lọ lati ibi?
Oriire! O kan pari boṣewa _fork -> oniye -> edit -> PR_ iṣan-iṣẹ ti iwọ yoo ba pade nigbagbogbo bi oluranlọwọ!
Ṣe ayẹyẹ ilowosi rẹ ki o pin pẹlu awọn ọrẹ ati awọn ọmọlẹyin rẹ nipa lilọ si [ohun elo wẹẹbu](https://firstcontributions.github.io#social-share).
O le darapọ mọ ẹgbẹ alailẹṣẹ wa ni ọran ti o nilo iranlọwọ eyikeyi tabi ni awọn ibeere eyikeyi.
[Darapọ mọ ẹgbẹ alailẹṣẹ](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYVk)
### [Awọn ohun elo afikun](../additional-material/git_workflow_scenarios/additional-material.md)
## Awọn olukọni Lilo Awọn irinṣẹ miiran
[Pada si oju-iwe akọkọ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-desktop-tutorial-np.md
+121
View File
@@ -0,0 +1,121 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# पहिलो योगदान(Contribution)
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
ओपन सोर्स(open source) भनेको सहकार्य र सँगै काम गर्नु हो । हामी नयाँ खुला स्रोत(open source) योगदानकर्ताहरू(contributors )ले सिक्ने र पहिलो पटक योगदान गर्ने तरिकालाई सरल बनाउन चाहन्थ्यौं।
लेखहरू(Articles) पढ्ने र ट्यूटोरियलहरू(Tutorials) हेर्ने बानीले मद्दत गर्न सक्छ, तर वास्तवमा कुनै पनि गडबड नगरी योगदान गर्नु त झनै राम्रो । यस परियोजनाको उद्देश्य मार्गनिर्देशन प्रदान गर्ने र सुरुवातकर्ताहरूले आफ्नो पहिलो योगदान(contribution) गर्ने तरिकालाई सरल बनाउने हो। याद गर्नुहोस् कि तपाई जति धेरै आराम गर्नुहुन्छ तपाईले राम्रोसँग सिक्नु हुन्छ। यदि तपाईं आफ्नो पहिलो योगदान(contribution) गर्न खोज्दै हुनुहुन्छ भने तलका सरल चरणहरू पालना गर्नुहोस्।
We promise you, it will be fun.
यदि तपाइँसँग तपाइँको कम्प्युटरमा GitHub Desktop छैन भने, [यहाँ बाट install गर्नुहोस् ](https://desktop.github.com/).
यदि तपाइँ 1.0 भन्दा पहिले GitHub desktop को संस्करण(version) प्रयोग गर्दै हुनुहुन्छ भने, [यो tutorial हेर्नुहोस्](github-desktop-old-version-tutorial.md).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## Repository लाई Fork गर्नुहोस्
यस repository page को Top मा रहेको `Fork` बटनमा क्लिक गरेर यो repository लाई Fork गर्नुहोस। यसले तपाईंको GitHub account मा यस repository प्रतिलिपि (copy) बनाउदछ ।
## Repository लाई Clone गर्नुहोस्
अब Fork गरेको repository लाई आफ्नो कम्प्युटरमा Clone गर्नुहोस्।
IMPORTANT: ORIGINAL REPO लाई clone नगर्नुहोला। आफ्नो fork गरेको REPO मा गएर clone गर्नुहोला।
repo लाई clone गर्न, "Clone or Download" मा क्लिक गर्नुहोस् र त्यसपछि "Open in Desktop" मा क्लिक गर्नुहोस्।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
एउटा pop up window खुल्छ त्यसमा "Open GitHubDesktop.exe" मा क्लिक गर्नुहोस्।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
"Open GitHubDesktop.exe" मा क्लिक गरेपछि repo को content हरु कम्प्युटरमा download हुन्छ।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
अब repo को content कम्प्युटरमा copy गरेपछि `first-contributions` नामको _repository_ GitHubDesktop मा देखिन्छ।
## Repository मा एउटा branch बनाउनुहोस्
अब माथिको "Current branch" आइकनमा क्लिक गरेर शाखा(branch) बनाउनुहोस् र त्यसपछि "New branch" मा क्लिक गर्नुहोस्:
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="make a branch" />
अब branch को नाम दिनुहोस् <add-your-name>. For example, "add-ram-regmi"
(ब्रान्चको नाममा add शब्दको आवश्यकता छैन, तर यसमा add समावेश गर्न उचित छ किनभने यस branch को उद्देश्य तपाईंको नामलाई contributors को सूची(list)मा थप्ने हो।)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
`Create branch`मा क्लिक गर्नुहोस्।
## आवश्यक परिवर्तनहरू गर्नुहोस् र ती परिवर्तनहरूलाई commit गर्नुहोस्
अब, history tab मा जानुहोस् र right click गरेर पाठ सम्पादक(text editor)मा `Contributors.md` फाइल खोल्नुहोस्। पृष्ठको तल स्क्रोल (Scroll) गर्नुहोस् र यसमा आफ्नो नाम थप्नुहोस्, त्यसपछि फाइल save गर्नुहोस्।
उदाहरण: यदि तपाईंको नाम Ram Regmi हो र github को username regmiram हो भने, थपेको नाम यस्तो देखिनु पर्छ।
\[Ram Regmi](https://github.com/regmiram)
तपाईंले Contributors.md मा परिवर्तनहरू भएको देख्न सक्नुहुन्छ र तिनीहरू Github Desktop मा थपिएका छन्।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
अब ती परिवर्तनहरू प्रतिबद्ध(commit) गर्नुहोस्:
_summary_ फिल्डमा "Add `<your-name>` to Contributors list" सन्देश(commit message) लेख्नुहोस्।
`<your-name>` लाई आफ्नो नामले बदल्नुहोस्।
`Commit to add-your-name` भन्ने बटनमा क्लिक गर्नुहोस्।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
तल, तपाइँ the commit has been created भनेर देख्न सक्नुहुन्छ।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit your changes" />
## GitHub मा परिवर्तनहरुलाई push गर्नुहोस।
File->Options मा क्लिक गर्नुहोस् र तपाईंको Github username र password टाइप गरि Github.com मा साइन इन गर्नुहोस्।।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in to Github" />
top right भएको `Publish` button मा क्लिक गर्नुहोस्।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push your changes" />
## Review को लागि तपाईंको परिवर्तनहरू पेश गर्नुहोस्।
यदि तपाईं आफ्नो गिटहब रिपोजिटोरी ( GitHub Repository) मा जानुहुन्छ भने, तपाइँले `Compare & pull request` बटन देख्नुहुनेछ। त्यस बटनमा क्लिक गर्नुहोस्।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
अब pull request पेश गर्नुहोस्।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
केहि समयमै म यस प्रोजेक्टको Master branch मा तपाईका सबै परिवर्तनहरू Merge गर्नेछु। परिवर्तनहरू merge भएपछि हजुरले एक notification इमेल(email) प्राप्त गर्नुहुनेछ।
## यहाँबाट कहाँ जाने?
बधाई छ! तपाईले Fork -> Clone -> Edit -> Pull Request कार्यप्रवाह(workflow) पूरा गर्नुभयो, जुन तपाई प्राय: एक योगदानकर्ता(contributor)को रूपमा गर्नुहुनेछ!
तपाईंले योगदान(contribution) दिनु भएकोमा खुशी मनाउनुहोस् र [web app](https://firstcontributions.github.io/#social-share) मा गएर आफ्नो friends and follower हरूमा पनि शेयर गर्नुहोस् ।
तपाइँलाई कुनै पनि मद्दत चाहिन्छ वा कुनै प्रश्न छ भने तपाइँ हाम्रो slack team मा सामेल हुन सक्नुहुनेछ। [join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
अब तपाईले अन्य प्रोजेक्टहरूमा योगदान दिन सुरु गर्नुहोस्। हामीले तपाईंले गर्न सक्नुहुने सजिलो समस्याहरू(issues)को साथमा प्रोजेक्टहरूको सूची संकलन गरेका छौ हेर्नुहोस् ।. [list of projects in the web app](https://firstcontributions.github.io/#project-list)।
### [थप सामग्री](../additional-material/git_workflow_scenarios/additional-material.md)
## अन्य उपकरणहरू प्रयोग गर्ने tutorial हरु
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-desktop-tutorial.cn.md
+126
View File
@@ -0,0 +1,126 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# 第一次做贡献
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
这是一个针对初次参与者的指南。
难。做任何事情的第一次总是难的。特别是在合作时，犯错并不是一件舒服的事情。但开源就是关于合作与共同工作的。我们想要简化新开源贡献者第一次学习和贡献的方式。
阅读文章和观看教程可以帮助，但实际操作而不搞砸任何事情会更好。这个项目旨在提供指导并简化新手做出他们的第一次贡献的方式。记住，你越放松，你学得就越好。如果你在寻找做出你的第一次贡献，只需跟随下面的简单步骤。我们保证这将是有趣的。
如果你的机器上没有GitHub Desktop，请[安装它](https://desktop.github.com/)。
如果你使用的是GitHub Desktop 1.0之前的版本，请[参考这个教程](github-desktop-old-version-tutorial.md)。
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## Fork this repository
通过点击这个页面右上角的 fork 按钮来 fork 这个repository。这将在你的账户中创建这个repository的一个副本。
## Clone the repository
现在将这个repository克隆到你的机器上。
重要提示：不要克隆原始repository。去你的 fork repository然后克隆它。
要克隆repository，点击“Clone or Download”然后点击“Open in Desktop”。
克隆这个repository
一个弹出窗口将打开。点击“Open GitHubDesktop.exe”。
克隆这个repository
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="克隆这个repository" />
在你点击“Open GitHubDesktop.exe”后，内容将被下载到你的计算机上。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="克隆这个repository" />
克隆这个repository
现在你已经将第一个贡献者仓库在github的内容复制到了你的计算机上。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="克隆这个repository" />
## Create a branch
现在通过点击顶部的“Current branch”图标然后点击“New branch”来创建一个分支：
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="创建一个分支" />
将你的分支命名为<add-your-name>。例如，“add-james-smith”
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="命名你的分支" />
点击 `Create branch`
## Make necessary changes and commit those changes
现在，转到历史标签页并通过右击然后在文本编辑器中打开Contributors.md文件。滚动到页面底部并添加你的名字，然后保存文件。
例如：如果你的名字是James Smith，它应该看起来像这样。
\[James Smith](https://github.com/jamessmith)
你可以看到Contributors.md有变化，它们已经被添加到Github Desktop。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="检查状态" />
现在提交这些变化：
在summary字段中写上"Add <your-name> to Contributors list"作为消息。
将<your-name>替换为你的名字。
点击写着Commit to add-your-name的按钮。
在底部，你可以看到已经创建了提交。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="提交你的变化" />
## Push changes to github
点击File->Options并登录到Github.com。输入你的Github用户名和密码。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="登录到Github" />
点击右上角的Publish按钮。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="推送你的变化" />
推送你的变化
## Submit your changes for review
如果你去你在github上的仓库，你会看到Compare & pull request按钮。点击那个按钮。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="创建一个pull请求" />
创建一个拉取请求
现在提交拉取请求。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="提交pull请求" />
很快我就会将所有的更改合并到这个项目的master分支中。一旦更改被合并，你将收到通知邮件。
## Where to go from here?
恭喜！你刚刚完成了你会经常遇到的作为贡献者的标准fork -> clone -> edit -> PR工作流程！
庆祝你的贡献，并通过去[web app](https://firstcontributions.github.io#social-share)与你的朋友和追随者分享。
如果你需要任何帮助或有任何问题，你可以加入我们的[slack团队](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)。
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials Using Other Tools
[回到主页](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-desktop-tutorial.ng_yr.md
+104
View File
@@ -0,0 +1,104 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Awọn ẹbun akọkọ
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Ojú-iṣẹ Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
O le. O jẹ lile nigbagbogbo ni igba akọkọ ti o ṣe nkan. Paapa nigbati o ba n ṣe ifowosowopo, ṣiṣe awọn aṣiṣe kii ṣe nkan ti o ni itunu. Ṣugbọn orisun ṣiṣi jẹ gbogbo nipa ifowosowopo & ṣiṣẹ papọ. A fẹ lati jẹ ki o rọrun ni ọna ti awọn oluranlọwọ orisun-ìmọ tuntun kọ ẹkọ & ṣe alabapin fun igba akọkọ.
Awọn nkan kika & wiwo awọn olukọni le ṣe iranlọwọ, ṣugbọn kini o dara julọ ju ṣiṣe nkan naa ni gangan laisi dabaru ohunkohun. Ise agbese yii ni ero lati pese itọnisọna & simplifying ọna ti awọn rookies ṣe ṣe ilowosi akọkọ wọn. Ranti diẹ sii ni ihuwasi ti o dara julọ ti o kọ ẹkọ. Ti o ba n wa ṣiṣe ilowosi akọkọ rẹ kan tẹle awọn igbesẹ ti o rọrun ni isalẹ. A ṣe ileri fun ọ, yoo jẹ igbadun.
Ti o ko ba ni Ojú-iṣẹ GitHub lori ẹrọ rẹ, [fi sii] (https://desktop.github.com/).
Ti o ba n lo ẹya ti tabili GitHub ṣaaju 1.0, [tọkasi ikẹkọ yii](github-desktop-old-version-tutorial.md). <img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt=" orita ibi ipamọ yii" />
## Orita ibi ipamọ yii
Fork repo yii nipa tite lori bọtini orita ni apa ọtun oke ti oju-iwe yii. Eyi yoo ṣẹda ẹda ibi ipamọ yii sinu akọọlẹ rẹ.
## Ti ẹda ibi ipamọ naa
Bayi clone repo yii si ẹrọ rẹ. PATAKI: MAA ṢE TI AWỌN REPO ORIGINAL. Lọ si orita rẹ ki o ṣe oniye rẹ. Lati ṣe oniye repo, tẹ lori "Clone tabi Download" ati lẹhinna tẹ "Ṣii ni Ojú-iṣẹ".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
Ferese agbejade yoo ṣii. Tẹ "Ṣii GitHubDesktop.exe".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
Lẹhin ti o tẹ “Ṣii GitHubDesktop.exe” awọn akoonu naa yoo ṣe igbasilẹ si kọnputa rẹ.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
Bayi o ti daakọ awọn akoonu ti ibi ipamọ awọn ifunni akọkọ ni github si kọnputa rẹ.
## Ṣẹda ẹka kan
Bayi ṣẹda ẹka kan nipa tite lori aami “Ẹka lọwọlọwọ” ni oke ati lẹhinna tẹ “Ẹka Tuntun”:
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
Tẹ 'Ṣẹda ẹka'
## Ṣe awọn ayipada to ṣe pataki ki o ṣe awọn ayipada yẹn
Bayi ṣii faili `Contributors.md` ni olootu ọrọ, yi lọ si isalẹ ti oju-iwe naa ki o fi orukọ rẹ kun, lẹhinna fi faili naa pamọ.
Apeere: Ti orukọ rẹ ba jẹ James Smith, O yẹ ki o dabi eleyi. \[James Smith](https://github.com/jamessmith) O le rii pe awọn ayipada wa si Contributors.md ati pe wọn ti ṣafikun si Ojú-iṣẹ Github.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
Bayi ṣe awọn ayipada wọnyi:
Kọ ifiranṣẹ naa "Ṣafikun `<orukọ-orukọ rẹ>` si atokọ Awọn oluranlọwọ” ni aaye _ akopọ _.
Ropo `<oruko-rẹ>` pẹlu orukọ rẹ.
Tẹ bọtini ti o sọ 'Ṣe lati fi-orukọ-rẹ'.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
Ni isalẹ, o le rii pe a ti ṣẹda ifaramọ naa.
<img style="osi;" src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt = "ṣe awọn ayipada rẹ" />
## Titari awọn ayipada si github
Tẹ Faili-> Awọn aṣayan ati wọle si Github.com. Tẹ orukọ olumulo Github ati ọrọ igbaniwọle sii.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt = "wọle si Github" />
Tẹ bọtini 'Tẹjade' ni apa ọtun oke.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt = "Titari awọn ayipada rẹ" />
## Firanṣẹ awọn ayipada rẹ fun atunyẹwo
Ti o ba lọ si ibi ipamọ rẹ lori github, iwọ yoo rii bọtini 'Afiwe & fa ìbéèrè'. tẹ lori wipe bọtini.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt = "ṣẹda ibeere fifa" />
Bayi fi ibeere fa silẹ.
<img src = "https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt = "fi ìbéèrè fa" />
Laipẹ Emi yoo dapọ gbogbo awọn ayipada rẹ si ẹka ọga ti iṣẹ akanṣe yii. Iwọ yoo gba imeeli iwifunni ni kete ti awọn ayipada ba ti dapọ.
## Nibo ni lati lọ lati ibi?
Oriire! O kan pari boṣewa _fork -> oniye -> edit -> PR_ iṣan-iṣẹ ti iwọ yoo ba pade nigbagbogbo bi oluranlọwọ!
Ṣe ayẹyẹ ilowosi rẹ ki o pin pẹlu awọn ọrẹ ati awọn ọmọlẹyin rẹ nipa lilọ si [ohun elo wẹẹbu](https://firstcontributions.github.io#social-share).
O le darapọ mọ ẹgbẹ alailẹṣẹ wa ni ọran ti o nilo iranlọwọ eyikeyi tabi ni awọn ibeere eyikeyi.
[Darapọ mọ ẹgbẹ alailẹṣẹ](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYVk)
### [Awọn ohun elo afikun](../additional-material/git_workflow_scenarios/additional-material.md)
## Awọn olukọni Lilo Awọn irinṣẹ miiran
[Pada si oju-iwe akọkọ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-desktop-tutorial.pt_br.md
+118
View File
@@ -0,0 +1,118 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# First Contributions
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
É difícil. É sempre difícil fazer algo pela primeira vez. Especialmente quando se está colaborando, cometer erros não é algo agradável. Mas _open source_ (código aberto) se trata de colaboração e de trabalharmos juntos. Queremos simplificar a forma com que novos colaboradores _open source_ aprendem e contribuem pela primeira vez.
Ler artigos e ver tutoriais pode ajudar, mas o que é melhor do que realmente pôr a mão na massa em um ambiente prático? Este projeto visa guiar e simplificar a forma com que os novatos fazem a sua primeira contribuição. Se quiser fazer a sua primeira contribuição, siga os passos abaixo.
Se você nao tem o Github desktop na sua máquina, [instale aqui](https://desktop.github.com/).
Se você está usando uma versão do Github desktop antes da 1.0, [consulte este tutorial](github-desktop-old-version-tutorial.md).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork este repositório" />
## Fork este repositório
Fork este repositório clicando no botão fork na parte superior direita dessa página.
Isso vai criar uma cópia desse repositório na sua conta.
## Clone este repositório
Agora clone esse repositório na sua máquina.
IMPORTANTE: NÃO CLONE O REPOSITÓRIO ORIGINAL. Vá para o seu fork e clone.
Para clonar esse repositório, clique em "Clone or Download" e então clique em "Open in Desktop".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone este repositório" />
Uma janela pop up vai aparecer. Clique em "Open GitHubDesktop.exe".
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone este repositório" />
Depois de clicar em "Open GitHubDesktop.exe" os arquivos serão baixados para o seu computador.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone este repositório" />
Agora você copiou os arquivos do repositório first-contributions no github para o seu computador.
## Criando uma branch (ramo)
Agora crie uma branch clicando na aba "Current branch" que fica no topo, depois clique em "New branch":
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="criar uma branch" />
Nomeie sua branch como <add-your-name>. Por exemplo, "add-james-smith"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="nomeie sua branch" />
Clique em `Create branch`
## Faça as mudanças necessárias e commit essas mudanças
Agora abra o arquivo `Contributors.md` em um editor de texto, vá para o final do arquivo e adicione seu nome, depois salve o arquivo.
Exemplo: Se o seu nome for James Smith, Deve ficar parecido com isso.
\[James Smith](https://github.com/jamessmith)
Você pode ver as alterações feitas em Contributors.md no Github Desktop.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="checar mudanças" />
Agora faça commit dessas alterações:
Escreva a mensagem "Add `<your-name>` to Contributors list" no campo _sumary_
Substitua `<your-name>` pelo seu nome.
Clique no botão que diz `Commit to add-your-name`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit suas alterações" />
Na parte inferior, você pode ver que o commit foi criado com sucesso.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit suas alterações" />
## Faça o push das mudanças no github
Clique em File -> Options e depois em sign-in to Github.com. Digite seu username e senha do Github.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in no Github" />
Clique no botão `Publish` na parte superior direita.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push suas alterações" />
## Envie suas alterações para review
Se você for até seu repositório no github, verá o botão `Compare & pull request`. Clique nesse botão
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="criando um pull request" />
Agora envie o pull request.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="enviando o pull request" />
Em breve estarei mesclando todas as suas alterações na branch Master do projeto. Você vai receber um email de notificação assim que as alterações forem integradas.
## Qual o próximo passo?
Parabéns! Você acabou de completar o fluxo _fork -> clone -> edit -> PR_ que encontrará diversas vezes como contribuidor!
Comemore sua contribuição e compartilhe com seus amigos e seguidores acessando o [web app](https://firstcontributions.github.io#social-share).
Você pode entrar na nossa equipe no Slack caso precise de alguma ajuda ou tenha alguma dúvida. [Entre no Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material adicional](../additional-material/git_workflow_senarios/additional-material.md)
## Tutoriais usando outras ferramentas
[Voltar a página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-desktop-tutorial.th.md
+121
View File
@@ -0,0 +1,121 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Contributions แรก
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
มันเป็นเรื่องยาก, มันยากเสมอในครั้งแรกที่คุณทำอะไร โดยเฉพาะเมื่อคุณทำงานร่วมกัน, การทำผิดไม่ใช่เรื่องที่สบายใจ แต่ โอเพนซอร์ส (open source) นั้นเป็นเรื่องของการทำงานร่วมกัน และเราจึงอยากให้ผู้ที่เข้ามาใหม่ได้เรียนรู้วิธีการ "คอนทริบิ้วต์" ผลงานร่วมกับผู้อื่นใน GitHub
การอ่านบทความและการดูวิดีโอสอนอาจจะช่วยให้คุณเข้าใจได้ดีขึ้น แต่มันยังไม่เท่ากับการทำจริง ๆ โดยไม่ทำผิดอะไร โครงการนี้จึงมีวัตถุประสงค์เพื่อให้ผู้ที่เข้ามาใหม่ได้เรียนรู้วิธีการ "คอนทริบิ้วต์" ผลงานร่วมกับผู้อื่นใน GitHub โดยที่ไม่พลาดอะไร
ยิ่งคุณผ่อนคลายมากเท่าไหร่ คุณก็ยิ่งเรียนรู้ได้ดีมากขึ้นเท่านั้น !
ถ้าคุณอยากร่วมส่งคอนทริบิ้วชั่นครั้งแรก ให้ทำตามขั้นตอนด้านล่างนี้ แล้วคุณจะเห็นว่ามันน่าสนุกมาก
ถ้าคุณยังไม่มี GitHub Desktop ในเครื่อง, [ดาวน์โหลดเลย](https://desktop.github.com/)
ถ้าคุณใช้ GitHub desktop เวอร์ชั่นเก่ากว่า 1.0, [อ่านที่นี่](github-desktop-old-version-tutorial.md)
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## กด "Fork" โปรเจ็คนี้
คุณสามารถแยกโปรเจ็คหลักออกไปทำที่แอคเคาน์ส่วนตัวของคุณได้ โดยการกดที่ปุ่ม "Fork" ที่ด้านบนขวาของหน้านี้ แล้วโปรเจ็คหลักจะถูกคัดลอกนำไปใส่ไว้ในแอคเคาน์ของคุณ
## กด "Clone" โปรเจ็คนี้
ได้เวลาคัดลอกโปรเจ็คนี้ไปที่เครื่องของคุณ
สำคัญ: อย่าคัดลอกโปรเจ็คหลัก ไปที่โปรเจ็คที่คุณคัดลอกไว้ในขั้นตอนก่อนหน้านี้ในแอคเคาน์ของคุณแล้วคัดลอกมัน
ในการคัดลอกโปรเจ็คนี้ไปยังเครื่องของคุณ กด "Clone or Download" แล้วกด "Open in Desktop"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
การแจ้งเตือนจะปรากฏขึ้นมา กดที่ "Open GitHubDesktop.exe"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
หลังจากคุณกด "Open GitHubDesktop.exe" โปรเจ็คจะถูกดาวน์โหลดไปยังเครื่องของคุณ
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
ตอนนี้คุณได้คัดลอกเนื้อหาของโปรเจ็ค first-contributions จาก github ไปยังเครื่องของคุณแล้ว
## สร้าง branch
ตอนนี้สร้าง branch โดยการคลิกที่ "Current branch" ที่ด้านบนแล้วคลิกที่ "New branch":
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="make a branch" />
ตั้งชื่อ branch ของคุณ <add-your-name>. ตัวอย่างเช่น "add-james-smith"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
กดที่ `Create branch`
## สร้างการเปลี่ยนแปลง และ commit การเปลี่ยนแปลง
ไปที่แท็บ `History` และเปิดไฟล์ `Contributors.md` ในตัวแก้ไขข้อความ (Text Editor)โดยการคลิกขวาและเปิดในตัวแก้ไขข้อความ (Text Editor) ลองเลื่อนไปที่ด้านล่างของหน้าจอและเพิ่มชื่อของคุณลงไป แล้วบันทึกไฟล์
ตัวอย่าง: ถ้าชื่อของคุณคือ James Smith ควรจะมีลักษณะดังนี้
\[James Smith](https://github.com/jamessmith)
You can see that there are changes to Contributors.md and they have been added to the Github Desktop.
คุณจะเห็นได้ว่ามีการเปลี่ยนแปลงในไฟล์ `Contributors.md` และมันถูกเพิ่มเข้าไปใน Github Desktop
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
Commit การเปลี่ยนแปลง:
เขียนข้อความ "Add `<your-name>` to Contributors list" ในช่อง _summary_
แทนที่ `<your-name>` ด้วยชื่อของคุณ
กดที่ปุ่มที่มีข้อความ `Commit to add-your-name`
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
ในด้านล่างคุณจะเห็นได้ว่าการ commit ถูกสร้างขึ้น
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit your changes" />
## "Push" โค้ดที่เปลี่ยนไปบน GitHub
กดที่ `File` -> `Options` และล็อกอินเข้าสู่ Github.com พิมพ์ชื่อผู้ใช้และรหัสผ่านของ Github ของคุณ
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in to Github" />
กดปุ่ม `Publish` ที่ด้านขวาบน
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push your changes" />
## ส่งผลงานของคุณและรอรีวิว
ถ้าคุณไปที่ repository ของคุณบน Github คุณจะเห็นปุ่ม `Compare & pull request` กดที่ปุ่มนั้น
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
ได้เวลาส่งผลงานของคุณ
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
ในเร็ว ๆ นี้เราจะรวมการเปลี่ยนแปลงทั้งหมดของคุณเข้าไปใน `master` ของโปรเจคนี้ คุณจะได้รับอีเมลแจ้งเตือนเมื่อมีการเปลี่ยนแปลงที่ถูก merge
## หลังจากนี้ตองทำอะไรต่อ?
Congrats! You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
ยินดีด้วย! คุณเพิ่งผ่านการทำงานที่มีมาตรฐาน _fork -> clone -> edit -> PR_ ที่คุณจะพบบ่อยๆ ในฐานะผู้มีส่วนร่วม(contributor)!
ฉลองการมีส่วนร่วมของคุณและแบ่งปันให้เพื่อน ๆ หรือผู้ติดตามของคุณ ได้ทราบโดยการไปที่ [หน้าเว็บนี้](https://firstcontributions.github.io#social-share)
คุณสามารถเข้าร่วม Slack ของเราได้หากคุณต้องการความช่วยเหลือหรือมีคำถามใด ๆ [เข้าร่วมทีม Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
### [ข้อมูลเพิ่มเติม](../additional-material/git_workflow_scenarios/additional-material.md)
## การคอนทริบิ้วต์โดยใช้เครื่องมืออื่น ๆ
[หลับไปที่หน้าหลัก](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-desktop-tutorial.vn.md
+134
View File
@@ -0,0 +1,134 @@
_Người dịch: [Ngo Phu Hien](https://github.com/FlopffyGrape)_ (một số đoạn dịch được lấy và chỉnh sửa từ [Tran Ly Vu](https://github.com/tranlyvu))
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Những đóng góp đầu tiên
| <img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="200"> | GitHub Desktop Edition |
| ----------------------------------------------------------------------------------------------- | ---------------------- |
Lần đầu tiên bạn làm gì cũng có thể gặp nhiều trở ngại. Khi bạn cộng tác cũng vậy, sai lầm là điều khó tránh khỏi. Vì vậy, chúng tôi muốn đơn giản hóa quy trình học và đóng góp của bạn vào những dự án mở.
Việc đọc hướng dẫn là có tác dụng, nhưng có gì tốt hơn là thực hành một cách thực tế? Dự án này nhằm mục đích hướng dẫn và đơn giản hóa cách để đóng góp vào những dự án mở trên Github cho người mới bắt đầu. Nếu bạn mong muốn thực hiện việc đóng góp đầu tiên của mình, chỉ cần làm theo các bước đơn giản bên dưới.
Nếu bạn muốn hiểu rõ hơn về cách Git và Github hoạt động, xem **Chú giải thuật ngữ Tiếng Anh** ở cuối trang.
Nếu bạn không có Github Desktop trên máy, [cài đặt](https://desktop.github.com/).
Nếu bạn đang dùng Github Desktop phiên bản 1.0 trở xuống, [nên xem hướng dẫn này](github-desktop-old-version-tutorial.md).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="Copy kho dự án" />
## Copy kho mã nguồn (Fork)
Copy kho mã nguồn này bằng cách nhấn vào nút Fork đầu trang này. Bản sao kho mã nguồn này sẽ được tạo ra trong tài khoản của bạn.
## Tải kho mã nguồn về máy (Clone)
Clone sẽ cho phép bạn tải kho mã nguồn (hay còn gọi là repository) về máy. (Download locally)
Để tải kho mã nguồn, nhấn vào "Clone or Download" sau đó nhấn "Open in Desktop"
LƯU Ý: Đừng tải kho mã nguồn gốc. Tải kho mã nguồn mà bạn vừa copy tại tài khoản của bạn
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-clonetodesktop.png" alt="clone this repository" />
Một cửa sổ sẽ hiện lên. Nhấn vào "Open GitHubDesktop.exe"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-open-githubdesktop.png" alt="clone this repository" />
Sau khi bạn nhấn nút "Open GitHubDesktop.exe", kho mã nguồn sẽ tự động tải về máy bạn.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-downloaded.png" alt="clone this repository" />
Bây giờ bạn đã tải thành công kho mã nguồn `first-contributions` trên github vào máy.
## Tạo chi nhánh (Branch)
Bước tiếp theo, bạn tạo branch mới bằng cách nhấn vào biểu tượng có dòng chữ "Current branch", sau đó nhấn "New branch"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch.png" alt="make a branch" />
Đặt tên branch vừa tạo là <add-tên-bạn>. Ví dụ, "add-hien-ngo"
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-create-branch-name.png" alt="name your branch" />
Nhấn `Create branch`
## Thực hiện những thay đổi cần thiết và commit các thay đổi vừa làm
Bây giờ mở tập tin Contributors.md và thêm tên của mình vào ở cuối tập tin. Sau đó lưu lại.
Ví dụ: Nếu tên bạn là Ngo Phu Hien, Bạn sẽ viết như này:
\[Ngo Phu Hien](https://github.com/hien-ngo29)
Lưu ý: https://github.com/hien-ngo29 là link vào tài khoản Github của bạn
Bạn có thể thấy những thay đổi của Contributors.md khi mở GithubDesktop.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-status.png" alt="check status" />
Bây giờ hãy commit các thay đổi đó. Commit sẽ lưu lại các thay đổi bạn vừa làm trên máy, nhưng chưa upload lên kho mã nguồn
Viết tin nhắn thay đổi: "Add `<tên-bạn>` to Contributors list" tại phần __summary__
Nhớ đổi `<tên-bạn>` thành đúng tên của bạn.
Nhấn `Commit to add-tên-bạn`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit1.png" alt="commit your changes" />
Ngay bên dưới, bạn sẽ thấy ngay commit đã được tạo.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-commit2.png" alt="commit your changes" />
## Đẩy các thay đổi lên Github (Push)
Push cho phép bạn upload các thay đổi bạn đã thực hiện trên máy lên kho mã nguồn chính.
Chọn File->Options và đăng nhập vào tài khoản Github.com của bạn. Gõ Github username và mật khẩu.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-sign-in.png" alt="log-in to Github" />
Nhấn vào nút `Publish` ở góc trên.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/dt1-publish1.png" alt="push your changes" />
## Gửi những thay đổi của bạn để xem xét (Pull Request)
Nếu bạn vào trang kho mã nguồn mà bạn vừa fork trên Github, bạn sẽ thấy nút `Compare & pull request`. Nhấn nút đó.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
Bây giờ gửi yêu cầu kéo. (Pull request)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
Tôi sẽ sớm hợp nhất (merge) tất cả các thay đổi của bạn vào nhánh chủ (master branch) của project này. Bạn sẽ nhận được email thông báo sau khi các thay đổi đã được hợp nhất.
## Đi đâu từ đây?
Chúc mừng! Bạn vừa hoàn thành quy trình đóng góp tiêu chuẩn: Copy kho mã nguồn (fork) -> Tải về máy (clone) -> Chỉnh sửa (edit) -> Gửi yêu cầu kéo (pull request) mà bạn sẽ làm thường xuyên khi đóng góp những dự án mở!
Hãy ăn mừng đóng góp của bạn và chia sẻ nó với bạn bè và những người theo dõi bằng cách truy cập [ứng dụng web](https://roshanjossey.github.io/first-contribution/#social-share).
Bạn có thể tham gia slack của chúng tôi trong trường hợp bạn cần trợ giúp hoặc có câu hỏi nào. [Tham gia slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Tài liệu](../additional-material/git_workflow_scenarios/additional-material.md)
## Hướng dẫn sử dụng các công cụ khác
[Quay lại trang chính](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
## _Chú giải thuật ngữ Tiếng Anh_
**Fork**: Copy kho mã nguồn của tài khoản Github khác sang tài khoản Github của bạn. Những thay đổi bạn làm trên kho mã nguồn vừa sao chép ở tài khoản sẽ không bị ảnh hưởng ở kho mã nguồn tài khoản bên kia (nhưng nhớ phải tạo branch mới).
**Clone**: Khác với nghĩa Tiếng Anh thông thường là *Sao chép*. Clone trên Git là tải kho mã nguồn về máy (Download locally). Vì thông thường khi thực hiện thay đổi trên kho mã nguồn thì bạn không nên thực hiện trực tiếp trên trang web của kho mã nguồn, tốt nhất nên tải về sau đó làm gì thì làm :).
**Branch**: Nôm na là phiên bản của kho mã nguồn. Có nhiều branch khác nhau do các tài khoản khác fork và tạo hay do chính chủ tạo. Branch thông thường bạn thấy khi mở kho mã nguồn là branch `master` hay `main`. Hay các branch khác là branch phiên bản:`v1`,`v2` ,.. hay branch `wip` (Working in progress (Đang làm) ). Các branch có thể được hợp nhất lại với nhau khi tạo Pull Request và được đồng ý bởi chính chủ. Bạn có thể chọn branch khi Fork, Clone, Commit, Push trên Github nhưng theo mặc định thì branch thông thường tên `master` hay `main`. Như ở hướng dẫn khi bạn fork mã nguồn thì phải tạo branch mới rồi thực hiện thay đổi lên branch đó chứ không thực hiện thay đổi lên branch `main` được (vì bạn không có quyền). Sau đó tạo Pull Request trên trang kho mã nguồn gốc và chờ được chủ đồng ý hợp nhất vào branch `main` .
**Commit**: Lưu các thay đổi mà bạn vừa làm trên máy nhưng chưa upload lên kho mã nguồn chính trên Github. Nói rõ và dể hiểu hơn, khi bạn clone kho mã nguồn lên máy, 1 thư mục ẩn sẽ được tạo là *.git* (để xem thư mục đó bạn chọn View->Hidden Items ở File Explorer). Thư mục này đóng vai trò quản lý các thay đổi bạn vừa làm trên máy hay nói nôm na là *file dự án* của Git. Các thay đổi mà bạn thực hiện sẽ được lưu trong thư mục *.git* đó sau khi bạn commit.
**Push**: Upload các thay đổi bạn vừa làm trên máy lên kho mã nguồn chính. Lưu ý phải commit các thay đổi trước khi push. Bạn có thể tạo nhiều commit rồi push 1 lần.
**Pull Request**: Sau khi bạn Fork một kho mã nguồn ở tài khoản khác và thực hiện thay đổi trên kho mã nguồn của tài khoản bạn. Bạn có thể tạo tin nhắn yêu cầu hợp nhất những thay đổi bạn thực hiện qua kho mã nguồn gốc bên tài khoản kia. Nói dễ hiểu là push các thay đổi của bạn thẳng lên mã nguồn gốc với điều kiện phải được chủ kho mã nguồn đồng ý và chấp nhận. Đây chính là phần thịt của đóng góp các dự án mở trên Github.
docs/gui-tool-tutorials/translations/github-windows-intellij-tutorial.pt_br.md
+126
View File
@@ -0,0 +1,126 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/assets/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
| <img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/9/9c/IntelliJ_IDEA_Icon.svg" width="40"> | IntelliJ IDEA |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
É difícil, sempre é difícil quando fazemos alguma coisa pela primeira vez. Especialmente quando você está colaborando, cometendo erros, não é nada confortável. No entanto, o open source é totalmente sobre colaboração & trabalho em equipe. Por isso, nós queremos simplificar a maneira como os novos colaboradores de código aberto aprendem & contribuem pela primeira vez.
Ler artigos & assistir a tutoriais até podem ajudar, mas o que é melhor do que fazer as coisas sem bagunçar nada. Este projeto tem como objetivo orientar & simplificar a forma como os iniciantes fazem a sua primeira contribuição. Lembre-se que você aprende melhor quando está relaxado. Se você deseja fazer sua primeira contribuição, basta seguir os passos abaixo. Nós prometemos a você que será divertido!
Se você ainda não tem o IntelliJ IDEA no seu computador, [instale-o](https://www.jetbrains.com/idea/download/#section=windows)
**Observação:** Este tutorial foi feito usando o IntelliJ IDEA (versão 2019.3.2) em um computador rodando Windows 10. Posteriormente neste tutorial, faremos uso de algumas teclas de atalho, que podem ser diferentes em outros sistemas operacionais (macOS / Linux).
## Faça o Fork deste repositório
<img align="right" width="300" src="https://camo.githubusercontent.com/fcf9a4ed664cc63de2fcb14d1135072ba6d4c74a8e9bdb224ad6ab1e72600c3b/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f666f726b2e706e67" alt="fork this repository" />
Faça um *fork* deste repositório clicando no botão *fork* (bifurcar) no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub.
O GitHub rastreia a relação entre seu repositório e o original, o qual você fez o *fork*. Você pode pensar em seu repositório como uma cópia de trabalho.
Muitos dos repositórios matrizes do GitHub (ou seja, aqueles que não são *Fork* de nenhum outro repositório) tem um pequeno grupo de pessoas que podem fazer commits de modificações diretamente. Todos os outros contribuidores devem fazer um *for* do repositório e fazer alterações no *fork*, em seguida, devem criar um Pull Request para solicitar um *Merge* (mesclagem) das modificações feitas no repositório original.
## Clone seu Repositório
<img align="right" width="300" src="https://camo.githubusercontent.com/4c3f7f1bec4f04db40ecf58dc2e19c2d8992f100f3bbbc4767a9d20b29f4a43d/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f636c6f6e652e706e67" alt="clone this repository" />
O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard".
**CUIDADO**: Um erro que os novatos costumam cometer é clonar o repo do qual você fez o fork, em vez de clonar seu repo. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório.
Agora abra o IntelliJ IDEA.
O IntelliJ IDEA permite que você faça um check out (em termos do Git clone) de um repositório existente e crie um novo projeto com base nos dados que você baixou.
No menu principal, escolha VCS | Get from Version Control ou, se nenhum projeto estiver aberto no momento, clique em Get from Version Control na tela inicial.
Na caixa de diálogo Get from Version Control dialog, especifique a URL do repositório remoto que deseja clonar (você pode clicar em Test para certificar-se de que a conexão com o repositório remoto pode ser estabelecida) ou selecione um dos serviços de hospedagem VCS à esquerda. Se você já estiver conectado ao serviço de hospedagem selecionado, a completion irá sugerir a lista de repositórios disponíveis que você pode clonar.
Clique em Clone. Se quiser criar um projeto IntelliJ IDEA com base nas fontes que você clonou, clique em Sim na caixa de diálogo de confirmação. O mapeamento de raiz do Git será automaticamente definido para o diretório raiz do projeto.
Se o seu projeto tiver submodelos, eles também serão clonados e automaticamente registrados como raízes do projeto.
**Importante**: certifique-se de que é o repositório é o fork e não o original, caso contrário, o procedimento não funcionará.
## Crie um branch
No Git, o processo de branching (ramificação) é um mecanismo poderoso que permite divergir da linha principal de desenvolvimento, por exemplo, quando você precisa trabalhar em um recurso ou congelar um determinado estado de uma base de código para um release e assim por diante.
No IntelliJ IDEA, todas as operações com branches são realizadas no pop-up Git Branches. Para ativá-lo, clique no widget Git na barra de status ou pressione Ctrl + Shift + `.
O nome do branch atual é exibido no widget do Git na barra de status.
No pop-up branch, escolha Novo branch.
Na caixa de diálogo que é aberta, especifique o nome do branch e certifique-se de que a opção Checkout branch esteja selecionada se você quiser alternar para esse branch.
A nova ramificação começará a partir do HEAD atual. Se você deseja iniciar um branch de um commit anterior ao invés do branch atual HEAD, selecione este commit na aba Log da janela da ferramenta de Controle de Versão Alt + 9 e escolha New Branch no menu de contexto.
## Faça as alterações necessárias
Abra ``Contributors.md`` e adicione seu nome em qualquer lugar do arquivo. Este arquivo contém GFM (GitHub Flavored Markdown), que é um tipo proprietário da sintaxe de [markdown](https://pt.wikipedia.org/wiki/Markdown).
Copie uma das linhas de outros contribuidores e modifique-a com seu nome para ter certeza que você obteve a sintaxe correta.
## Commit & Push modificações para o GitHub
Selecione os arquivos que deseja commitar ou uma lista de alterações inteira na guia Local Changes da janela da ferramenta de controle de versão Alt + 9 e pressione Ctrl + K ou clique no botão Commit na barra de ferramentas.
A caixa de diálogo Commit Changes abrira e listara todos os arquivos que foram modificados desde o último commit, bem como todos os arquivos não versionados recém-adicionados.
Insira uma mensagem de commit que faça sentido.
Você pode clicar em Commit Message history (Confirmar histórico de mensagens) Ctrl + M para escolher na lista de mensagens de commits recentes.
Você também pode editar a mensagem de commit mais tarde, antes de enviar o commit.
Pressione Ctrl + Shift + K ou escolha VCS | Git | Push from the main menu. A caixa de diálogo Push Commits é aberta, mostrando todos os repositórios Git (para projetos de vários repositórios) e listando todos os commits feitos no branch atual em cada repositório desde o último push.
## Envie suas alterações para revisão
Neste ponto, você concluiu a alteração, mas ela ainda está apenas no seu repo. Esta etapa mostrará como enviar uma solicitação ao administrador do repo matriz para mesclar sua alteração.
Em seu repo no GitHub, você verá o botão `Compare & pull request` ao lado da notificação do novo branch, clique nesse botão.
<img src="https://camo.githubusercontent.com/ca3b1cefece5f3b9b3435020e6a357ca024cda5bd2b1e140a15170fcd1ec5381/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f636f6d706172652d616e642d70756c6c2e706e67" alt="create a pull request" />
Agora submeta o pull request.
<img src="https://camo.githubusercontent.com/71401ba5551a64aeac3838825a52ce7a7597cd8b54a0d7200d9454e2cbfbb13f/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f7375626d69742d70756c6c2d726571756573742e706e67" alt="submit pull request" />
Em breve estarei mesclando todas as suas alterações no branch master deste projeto. Você receberá um e-mail de notificação assim que as alterações forem integradas.
## Para onde ir agora?
Parabéns! Você acabou de completar o padrão _fork -> clone -> edit -> PR_ workflow que você encontrará frequentemente como um contribuidor!
Comemore sua contribuição e compartilhe-a com seus amigos e seguidores acessando o [web app](https://firstcontributions.github.io/#social-share).
Você pode se juntar a nossa equipe slack caso precise de alguma ajuda ou tenha alguma dúvida. [Junte-se ao time slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
Agora vamos começar a contribuir para outros projetos, compilamos uma lista de projetos com questões fáceis para você começar. [Confira a lista de projetos no web app](https://firstcontributions.github.io/#project-list).
### [Material Adicional](../../additional-material/translations/Portugues/additional-material.pt_br.md).
## Tutoriais usando outras ferramentas
[Voltar a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md)
## Autopromoção
Se você gostou deste projeto, de star no GitHub. Se você gostou dessa tradução me siga no GitHub [Vitor Matias](https://github.com/VitorCMatias).
docs/gui-tool-tutorials/translations/github-windows-vs-code-tutorial-hi.md
+116
View File
@@ -0,0 +1,116 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/CodeWithAjaySaini)
# First Contributions
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
यह मुश्किल है। पहली बार जब आप कुछ करते हैं तो यह हमेशा कठिन होता है। खासकर जब आप सहयोग कर रहे हों, तो गलतियाँ करना सहज बात नहीं है। लेकिन ओपन सोर्स सहयोग और एक साथ काम करने के बारे में है। हम नए ओपन-सोर्स योगदानकर्ताओं के पहली बार सीखने और योगदान करने के तरीके को सरल बनाना चाहते थे।
लेख पढ़ना और ट्यूटोरियल देखना मदद कर सकता है, लेकिन वास्तव में कुछ भी गड़बड़ किए बिना सामान करने से बेहतर क्या हो सकता है। इस परियोजना का उद्देश्य मार्गदर्शन प्रदान करना और धोखेबाज़ों द्वारा अपना पहला योगदान देने के तरीके को सरल बनाना है। याद रखें कि आप जितने अधिक आराम से होंगे, आप उतना ही बेहतर सीखेंगे। यदि आप अपना पहला योगदान करना चाहते हैं, तो बस नीचे दिए गए सरल चरणों का पालन करें। हम आपसे वादा करते हैं, यह मजेदार होगा।
यदि आपकी मशीन पर विजुअल स्टूडियो कोड नहीं है, [install it](https://code.visualstudio.com/download).
**सूचना:** यह ट्यूटोरियल विंडोज 10 मशीन पर विजुअल स्टूडियो कोड (संस्करण 1.27.2) का उपयोग करके बनाया गया था। बाद में इस ट्यूटोरियल में हम कुछ कीबोर्ड शॉर्टकट का उपयोग करेंगे। ये अन्य ऑपरेटिंग सिस्टम (मैकोज़/लिनक्स) के साथ-साथ कीबोर्ड भाषा (यूके, डीई, आदि) पर भिन्न हो सकते हैं। आप कमांड पैलेट में "शॉर्टकट" खोजकर अपने शॉर्टकट की सूची देख सकते हैं।
## इस भंडार को फोर्क करें
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
इस रेपो को फोर्क करने के लिए इस पेज के ऊपर दाईं ओर फोर्क बटन पर क्लिक करें। यह आपके GitHub खाते में इस रिपॉजिटरी की एक प्रति बनाएगा।
गिटहब आपके रेपो और उस रेपो के बीच संबंधों का ट्रैक रखता है जिसे आपने इसे फोर्क किया है। आप अपने रेपो को एक कार्यशील प्रति के रूप में सोच सकते हैं।
अधिकांश शीर्ष-स्तरीय गिटहब रेपो (यानी किसी अन्य रेपो से फोर्क नहीं किए गए) में लोगों की एक छोटी सी कोर टीम होती है जो सीधे बदलाव कर सकती है। अन्य सभी योगदानकर्ताओं को रेपो को फोर्क करना होगा और फोर्क में परिवर्तन करना होगा, फिर एक पुल अनुरोध बनाना होगा ताकि उनके परिवर्तनों को शीर्ष-स्तरीय रेपो में वापस विलय करने के लिए कहा जा सके। यदि शीर्ष-स्तरीय रेपो व्यवस्थापक परिवर्तनों को पसंद करता है तो उन्हें विलय कर दिया जाएगा और आपको तुरंत प्रसिद्धि और भाग्य प्राप्त होगा! इसे बाद में कैसे करें, इसके बारे में अधिक।
## अपने भंडार को क्लोन करें
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
अगला कदम अपने रेपो को अपनी मशीन पर क्लोन करना है ताकि आप बदलाव करना शुरू कर सकें। वीएस कोड को आपके रेपो के यूआरएल की जरूरत है, इसलिए "क्लोन" बटन पर क्लिक करें और फिर "क्लिपबोर्ड पर कॉपी करें" आइकन पर क्लिक करें।
**सावधान:** एक गलती जो नए योगदानकर्ता अक्सर करते हैं, वह है रेपो का क्लोन बनाना जो आपने अपने रेपो को क्लोन करने के बजाय _from_ को फोर्क किया था। अपने ब्राउज़र के एड्रेस बार की जाँच करें और सुनिश्चित करें कि आप अपने रेपो की क्लोनिंग कर रहे हैं।
अब विजुअल स्टूडियो कोड खोलें। वीएस कोड का वेलकम पेज खुल जाएगा। वहां से नीचे दिखाए गए बार को खोलने के लिए `F1` दबाएं। ध्यान दें कि टेक्स्ट फ़ील्ड में पहले से ही एक `>` (इससे बड़ा) चिन्ह है। आप `CTRL-P` दबाकर इनपुट प्रॉम्प्ट पर भी जा सकते हैं और फिर `>` वर्ण टाइप कर सकते हैं।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
आप देख सकते हैं कि नीचे सूचीबद्ध कुछ अस्पष्ट आदेश पहले से ही हैं। वे मेरे हाल ही में उपयोग किए गए आदेश हैं। तो बस उनकी परवाह मत करो।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
अब 'गिट क्लोन' टाइप करें, केवल 'गिट' या 'क्लोन' (यह एक खोज की तरह काम करता है)।
प्रविष्टि `गिट: क्लोन` का चयन करें और `एंटर` दबाएं
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
अपनी रिपॉजिटरी का URL पेस्ट करें और `Enter` दबाएं। यह एक फ़ाइल एक्सप्लोरर खोलेगा जहाँ आप तब चुन सकते हैं जहाँ Git रिपॉजिटरी को संग्रहीत किया जाना चाहिए।
**महत्वपूर्ण**: सुनिश्चित करें कि यह फोर्कड रिपोजिटरी है और मूल नहीं है, अन्यथा यह काम नहीं करेगा।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
आपको विजुअल स्टूडियो कोड के नीचे दाईं ओर एक स्टेटस पॉपअप देखना चाहिए। इसके समाप्त होने के बाद, आप संवाद में बटनों का उपयोग करके क्लोन रिपॉजिटरी (अब आपकी मशीन पर एक फ़ोल्डर) खोल सकते हैं।
## एक शाखा बनाएं
`F1` दबाकर फिर से कमांड पैलेट खोलें। `शाखा` टाइप करें और वहां से `शाखा बनाएं` कमांड चुनें। अगले चरण में अपनी नई शाखा का नाम टाइप करें, उदाहरण के लिए `ऐड-डेविड-क्रोल`। एंटर दबाएं और ब्रांच बन जाएगी. The branch is also already checked out. [What does checkout mean?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## आवश्यक परिवर्तन करें
`Contributors.md` खोलें और फ़ाइल में कहीं भी अपना नाम जोड़ें। इस फ़ाइल में GFM (GitHub Flavored Markdown) है जो <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a> सिंटैक्स का मालिकाना स्वाद है।
अन्य योगदानकर्ताओं में से एक की प्रतिलिपि बनाएँ&apos; लाइनों और इसे अपने नाम के साथ संशोधित करें यह सुनिश्चित करने के लिए कि आपको सिंटैक्स सही मिलता है - यह पिक्य हो सकता है।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## गिटहब में बदलाव करें और पुश करें
वीएस कोड के बाईं ओर एक मेनू है जिसमें 5 आइकन प्रदर्शित होते हैं। संस्करण नियंत्रण/स्रोत नियंत्रण चिह्न का चयन करें।
(शॉर्टकट : Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
फ़ाइल एक्सप्लोरर उन सभी फाइलों को प्रदर्शित करता है जिन्हें अंतिम प्रतिबद्धता के बाद बदल दिया गया था। फाइलों को मँडराकर और `+` (प्लस) पर क्लिक करके फाइलों का मंचन किया जाता है।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
एक्सप्लोरर के ऊपर लाइन में कुछ टाइप करें और चेकमार्क दबाएं। परिवर्तन अब आपकी स्थानीय प्रति के लिए प्रतिबद्ध हैं। अब परिवर्तनों को वापस GitHub पर धकेलना होगा।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
मेनू खोलने के लिए थ्री-डॉट आइकन का उपयोग करें जहां आप `पब्लिश ब्रांच` विकल्प का चयन करते हैं। यह आपके GitHub क्रेडेंशियल्स को डालने के लिए एक डायलॉग खोलना चाहिए।
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="स्टैश की गई फ़ाइलें ">
## समीक्षा के लिए अपने परिवर्तन सबमिट करें
इस बिंदु पर आपने अपना परिवर्तन पूरा कर लिया है लेकिन यह अभी भी केवल आपके रेपो में रहता है। यह चरण आपको दिखाएगा कि अपने परिवर्तन को मर्ज करने के लिए शीर्ष-स्तरीय रेपो के व्यवस्थापक को अनुरोध कैसे सबमिट करें।
गिटहब पर अपने रेपो में आपको नई शाखा अधिसूचना के बगल में `तुलना और पुल अनुरोध` बटन दिखाई देगा। उस बटन पर क्लिक करें।
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="एक पुल अनुरोध बनाएं" />
अब पुल रिक्वेस्ट सबमिट करें।
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="पुल अनुरोध सबमिट करें" />
जल्द ही मैं आपके सभी परिवर्तनों को इस परियोजना की मास्टर शाखा में मिला दूंगा। परिवर्तनों को मर्ज कर दिए जाने के बाद आपको एक सूचना ईमेल प्राप्त होगी।
## यहाँ से कहाँ जाएं?
बधाई! आपने अभी-अभी मानक _fork -> क्लोन -> संपादित करें -> PR_ वर्कफ़्लो पूरा किया है जिसका आप अक्सर एक योगदानकर्ता के रूप में सामना करेंगे!
अपने योगदान का जश्न मनाएं और [वेब ऐप](https://firstcontributions.github.io#social-share) पर जाकर इसे अपने दोस्तों और अनुयायियों के साथ साझा करें।
यदि आपको किसी सहायता की आवश्यकता हो या कोई प्रश्न पूछना हो तो आप हमारी सुस्त टीम में शामिल हो सकते हैं। [स्लैक टीम में शामिल हों](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)।
### [अतिरिक्त सामग्री](../additional-material/git_workflow_scenarios/additional-material.md)
## अन्य टूल्स का उपयोग करने वाले ट्यूटोरियल
[मुख्य पृष्ठ पर वापस जाएं](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-windows-vs-code-tutorial.ml.md
+115
View File
@@ -0,0 +1,115 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# ആദ്യ സംഭാവനകൾ (First Contributions)
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
ആദ്യമായി ഒരു കാര്യം ചെയ്യുക എന്നുള്ളത് വളരെ ബുദ്ധിമുട്ടാണ്. പ്രത്യേകിച്ച്, മറ്റു പലരുടെയും ഒപ്പം ജോലി ചെയ്യുമ്പോൾ തെറ്റ് വരുന്നത് അത്ര സുഖകരമായ കാര്യം അല്ല. സ്വതന്ത്ര സോഫ്റ്റ്‌വെയറിലേക്ക് ആദ്യമായി സംഭാവന ചെയ്യുന്നവർക്ക് അതിനെ പറ്റി പഠിക്കാനും പങ്കാളിയാകുവാനും വേണ്ടി കുറച്ച്‌കൂടെ എളുപ്പമായ എന്തെങ്കിലും ഉണ്ടാക്കണമെന്നായിരുന്നു ഞങ്ങളുടെ ആഗ്രഹം.
ലേഖനങ്ങൾ വായിക്കുന്നതും വീഡിയോകൾ കാണുന്നതും ഒക്കെ സഹായകരമാണ്. പക്ഷേ ചെയ്ത് തന്നെ പഠിക്കുന്നതല്ലേ ഏറ്റവും നല്ലത്? ഈ പ്രൊജക്റ്റ് ഇതിനെ പറ്റി പരിചയം ഇല്ലാത്ത ഒരാൾക്ക് ആദ്യത്തെ സംഭാവന നല്കാൻ ഉള്ള ഒരു വഴികാട്ടി ആണ്. നിങ്ങൾ എത്രത്തോളം സ്വസ്‌ഥമായിരിക്കുന്നുവോ അത്രയും നന്നായി പഠിക്കുമെന്ന് ഓർക്കുക. നിങ്ങളും നിങ്ങളുടെ ആദ്യ സംഭാവന നൽകാൻ ആഗ്രഹിക്കുന്നുവെങ്കിൽ, താഴെ പറയുന്നത് പോലെ ചെയ്യുക. ഞങ്ങൾ നിങ്ങൾക്ക് വാഗ്ദാനം ചെയ്യുന്നു, ഇത് രസകരമായിരിക്കും.
നിങ്ങളുടെ മെകമ്പ്യൂട്ടറിൽ വിഷ്വൽ സ്റ്റുഡിയോ കോഡ് ഇല്ലെങ്കിൽ, [ഇത് ഇൻസ്റ്റാൾ ചെയ്യുക](https://code.visualstudio.com/download).
**അറിയിപ്പ്:** ഈ പരിശീലനപദ്ധതി ഒരു Windows 10 മെഷീനിൽ വിഷ്വൽ സ്റ്റുഡിയോ കോഡ് (പതിപ്പ് 1.27.2) ഉപയോഗിച്ചാണ് നിർമ്മിച്ചിരിക്കുന്നത്. ഈ ട്യൂട്ടോറിയലിൽ ഞങ്ങൾ ചില കീബോർഡ് കുറുക്കുവഴികൾ ഉപയോഗിക്കുന്നതായിരിക്കും. മറ്റ് ഓപ്പറേറ്റിംഗ് സിസ്റ്റങ്ങളിലും (macOS/Linux) കീബോർഡ് ഭാഷയിലും (UK, DE, മുതലായവ) ഇവ വ്യത്യാസമായിരിക്കാം. കമാൻഡ് പാലറ്റിൽ "shortcut" തിരഞ്ഞുകൊണ്ട് നിങ്ങൾക്ക് കുറുക്കുവഴികളുടെ പട്ടികയിലൂടെ കടന്നുപോകാം.
## ഈ റെപ്പോസിറ്ററി ഫോർക്ക് (fork) ചെയ്യുക
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
ഈ പേജിന്റെ ഏറ്റവും മുകളിൽ ഉള്ള ഫോർക്ക് ബട്ടൺ ഉപയോഗിച്ച് ഈ റെപ്പോസിറ്ററി ഫോർക്ക് ചെയ്യുക. ഇങ്ങനെ ചെയ്യുമ്പോൾ നിങ്ങളുടെ അക്കൗണ്ടിൽ ഈ റെപ്പോസിറ്ററിയുടെ ഒരു പകർപ്പ് സൃഷ്ടിക്കപ്പെടുന്നു.
GitHub നിങ്ങളുടെ റിപ്പോയും നിങ്ങൾ ഫോർക്ക് ചെയ്ത റിപ്പോയും തമ്മിലുള്ള ബന്ധത്തിന്റെ ട്രാക്ക് സൂക്ഷിക്കുന്നു. നിങ്ങളുടെ റിപ്പോ ഒരു പ്രവർത്തന പകർപ്പായി നിങ്ങൾക്ക് ചിന്തിക്കാം.
മിക്ക ഉയർന്ന തലത്തിലുള്ള GitHub റിപ്പോകൾക്കും (അതായത് മറ്റേതെങ്കിലും റിപ്പോയിൽ നിന്നും ഫോർക്ക് ചെയ്യാത്തവ) നേരിട്ട് മാറ്റങ്ങൾ വരുത്താൻ കഴിയുന്ന ഒരു ചെറിയ കോർ സംഘം ഉണ്ട്. മറ്റെല്ലാ സംഭാവകരും റിപ്പോ ഫോർക്ക് ചെയ്യുകയും ഫോർക്കിൽ മാറ്റങ്ങൾ വരുത്തുകയും വേണം, തുടർന്ന് അവരുടെ മാറ്റങ്ങൾ ഈ ഉയർന്ന തലത്തിലുള്ള റിപ്പോയിലേക്ക് വീണ്ടും ലയിപ്പിക്കുന്നതിനുവേണ്ടി ഒരു പുൾ അഭ്യർത്ഥന(pull request) സൃഷ്ടിക്കണം. ഉയർന്ന തലത്തിലുള്ള റിപ്പോ അഡ്‌മിനിസ്‌ട്രേറ്റർക്ക് മാറ്റങ്ങൾ ഇഷ്‌ടപ്പെട്ടാൽ അവ ലയിപ്പിക്കുകയും നിങ്ങൾക്ക് തൽക്ഷണം പ്രശസ്തി ലഭിക്കുകയും ചെയ്യും!
## ഈ റെപ്പോസിറ്ററി ക്ലോൺ (clone) ചെയ്യുക
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
നിങ്ങളുടെ മെഷീനിലേക്ക് നിങ്ങളുടെ റിപ്പോ ക്ലോൺ ചെയ്യുക എന്നതാണ് അടുത്ത ഘട്ടം, അതുവഴി നിങ്ങൾക്ക് മാറ്റങ്ങൾ വരുത്താൻ ആരംഭിക്കാം. VS കോഡിന് നിങ്ങളുടെ റിപ്പോയുടെ URL ആവശ്യമാണ്, അതിനാൽ കോഡ് ബട്ടണിൽ ക്ലിക്കുചെയ്‌ത് "copy to clipboard" ഐക്കണിൽ ക്ലിക്കുചെയ്യുക.
**സൂക്ഷിക്കുക:** പുതിയ സംഭാവകർ പലപ്പോഴും ചെയ്യുന്ന ഒരു തെറ്റ് എന്തെന്നാൽ, നിങ്ങളുടെ റിപ്പോ ക്ലോൺ ചെയ്യുന്നതിനുപകരം നിങ്ങൾ _ഫോർക്ക് ചെയ്യാൻ ഉപയോഗിച്ച റിപ്പോ_ ക്ലോൺ ചെയ്യുക എന്നതാണ്. നിങ്ങളുടെ ബ്രൗസറിന്റെ address ബാർ പരിശോധിച്ച് നിങ്ങളുടെ റിപ്പോ തന്നെയാണ് ക്ലോൺ ചെയ്യുന്നതെന്ന് ഉറപ്പാക്കുക.
ഇപ്പോൾ വിഷ്വൽ സ്റ്റുഡിയോ കോഡ് തുറക്കുക. വിഎസ് കോഡിന്റെ സ്വാഗത പേജ് പോപ്പ് അപ്പ് ചെയ്യും. താഴെ കാണിച്ചിരിക്കുന്ന ബാർ തുറക്കാൻ അവിടെ നിന്ന് `F1` അമർത്തുക. ടെക്സ്റ്റ് ഫീൽഡിൽ ഇതിനകം തന്നെ `>` ചിഹ്നമുണ്ടെന്ന് ശ്രദ്ധിക്കുക. മറ്റൊരു മാർഗ്ഗം `CTRL-P` അമർത്തിക്കൊണ്ട് നിങ്ങൾ ഇൻപുട്ട് പ്രോംപ്റ്റിലേക്ക് പോയിട്ട്, `>` ടൈപ്പ് ചെയ്യുന്നതാണ്.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
ഈ ചിത്രത്തിൽ ചില അവ്യക്തമായ കമാൻഡുകൾ താഴെ ലിസ്റ്റ് ചെയ്തിരിക്കുന്നത് നിങ്ങൾ ശ്രദ്ധിച്ചേക്കാം. ഞാൻ അടുത്തിടെ ഉപയോഗിച്ച കമാൻഡുകൾ ഇവയാണ്. അതുകൊണ്ട് അവരെ കാര്യമാക്കേണ്ട.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
അടുത്തതായി `git clone` എന്ന് ടൈപ്പ് ചെയ്യുക.
'Git: Clone' എന്ന എൻട്രി തിരഞ്ഞെടുത്ത് 'Enter' അമർത്തുക.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
നിങ്ങളുടെ റിപ്പോസിറ്ററിയുടെ URL പേസ്റ്റ് ചെയ്യുക, `Enter` അമർത്തുക. ഇത് ഒരു ഫയൽ എക്സ്പ്ലോറർ തുറക്കും, അവിടെ നിങ്ങൾക്ക് Git റിപ്പോസിറ്ററി എവിടെ സൂക്ഷിക്കണമെന്ന് തിരഞ്ഞെടുക്കാം.
**അറിയിപ്പ്**: ഇത് ഫോർക്ക്ഡ് റിപ്പോസിറ്ററി ആണെന്നും ഒറിജിനൽ അല്ലെന്നും ഉറപ്പാക്കുക, അല്ലാത്തപക്ഷം ഇത് പ്രവർത്തിക്കില്ല.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
വിഷ്വൽ സ്റ്റുഡിയോ കോഡിന്റെ ചുവടെ വലതുവശത്ത് നിങ്ങൾ ഒരു സ്റ്റാറ്റസ് പോപ്പ്അപ്പ് കാണും. ഇത് പൂർത്തിയായ ശേഷം, ഡയലോഗിലെ ബട്ടണുകൾ ഉപയോഗിച്ച് നിങ്ങൾക്ക് ക്ലോൺ ചെയ്ത റിപ്പോസിറ്ററി (ഇപ്പോൾ നിങ്ങളുടെ മെഷീനിലെ ഒരു ഫോൾഡർ) തുറക്കാൻ കഴിയും.
## ഒരു ശാഖ (ബ്രാഞ്ച്, Branch) ഉണ്ടാക്കുക
`F1` അമർത്തി കമാൻഡ് പാലറ്റ് വീണ്ടും തുറക്കുക. `git branch` എന്ന് ടൈപ്പ് ചെയ്ത് അവിടെ നിന്ന് `create branch` എന്ന കമാൻഡ് തിരഞ്ഞെടുക്കുക. അടുത്ത ഘട്ടത്തിൽ നിങ്ങളുടെ പുതിയ ബ്രാഞ്ചിന്റെ പേര് ടൈപ്പ് ചെയ്യുക, ഉദാഹരണത്തിന് `add-david-kroell`. Enter അമർത്തുക, ബ്രാഞ്ച് സൃഷ്ടിക്കപ്പെടും. ബ്രാഞ്ചും ഇതിനകം ചെക്ക് ഔട്ട് ആയി. [ചെക്ക്ഔട്ട് എന്നാൽ എന്താണ് അർത്ഥമാക്കുന്നത്?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## ആവശ്യമായ മാറ്റങ്ങൾ വരുത്തുക
`Contributors.md` തുറന്ന് ഫയലിൽ എവിടെയും നിങ്ങളുടെ പേര് ചേർക്കുക. ഈ ഫയലിൽ <a href="https://en.wikipedia.org/wiki/Markdown">മാർക്ക്ഡൗൺ</a> വാക്യഘടനയുടെ ഉടമസ്ഥാവകാശമുള്ള GFM (GitHub Flavored Markdown) അടങ്ങിയിരിക്കുന്നു.
നിങ്ങൾക്ക് വാക്യഘടന ശരിയാണെന്ന് ഉറപ്പാക്കാൻ മറ്റ് സംഭാവകരുടെ ലൈനുകളിൽ ഒന്ന് പകർത്തി അത് നിങ്ങളുടെ പേരിനൊപ്പം പരിഷ്‌ക്കരിക്കുക. മാറ്റം രജിസ്റ്റർ ചെയ്യുന്നതിനായി ഫയൽ save ചെയ്യുക.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## GitHub-ലേക്ക് മാറ്റങ്ങൾ commit ചെയ്ത ശേഷം push ചെയ്യുക
വിഎസ് കോഡിന്റെ ഇടതുവശത്ത് 5 ഐക്കണുകൾ പ്രദർശിപ്പിച്ചിരിക്കുന്ന ഒരു മെനുവാണ്.version control/Source Control ഐക്കൺ തിരഞ്ഞെടുക്കുക.
(കുറുക്കുവഴി: Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
അവസാന കമ്മിറ്റിന് ശേഷം മാറ്റിയ എല്ലാ ഫയലുകളും file explorer പ്രദർശിപ്പിക്കുന്നു. ഫയലിന്റെ പേരിനു മുകളിൽ കഴ്‌സർ ഹോവർ ചെയ്ത ശേഷം `+` (പ്ലസ്) ക്ലിക്ക് ചെയ്യുന്നതിലൂടെ ഫയലുകൾ staged ആയി മാറുന്നു.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
എക്സ്പ്ലോററിന് മുകളിലുള്ള വരിയിൽ എന്തെങ്കിലും ടൈപ്പ് ചെയ്ത് ചെക്ക്മാർക്ക് അമർത്തുക. മാറ്റങ്ങൾ ഇപ്പോൾ നിങ്ങളുടെ പ്രാദേശിക പകർപ്പിൽ committed ആയി. ഇപ്പോൾ മാറ്റങ്ങൾ GitHub-ലേക്ക് തിരികെ മാറ്റേണ്ടതുണ്ട്.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
മെനു തുറക്കാൻ മൂന്ന് കുത്തുകളുള്ള ഐക്കൺ ഉപയോഗിക്കുക, തുടർന്ന് നിങ്ങൾ `പബ്ലിഷ് ബ്രാഞ്ച്` ഓപ്‌ഷൻ അമർത്തുക. നിങ്ങളുടെ GitHub ക്രെഡൻഷ്യലുകൾ ഉൾപ്പെടുത്തുന്നതിന് ഇത് ഒരു ഡയലോഗ് തുറക്കും.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## നിങ്ങളുടെ മാറ്റങ്ങൾ അവലോകനത്തിനായി സമർപ്പിക്കുക
ഈ സമയത്ത് നിങ്ങൾ നിങ്ങളുടെ മാറ്റം പൂർത്തിയാക്കി, പക്ഷേ അത് ഇപ്പോഴും നിങ്ങളുടെ റിപ്പോയിൽ മാത്രമേ വസിക്കുന്നുള്ളൂ. നിങ്ങളുടെ മാറ്റം ലയിപ്പിക്കുന്നതിന് ഉയർന്ന തലത്തിലുള്ള റിപ്പോയുടെ അഡ്മിനിസ്ട്രേറ്റർക്ക് ഒരു അഭ്യർത്ഥന സമർപ്പിക്കുന്നത് എങ്ങനെയെന്ന് ഈ ഘട്ടം നിങ്ങളെ കാണിക്കും.
GitHub-ലെ നിങ്ങളുടെ റിപ്പോയിൽ പുതിയ ബ്രാഞ്ച് notification അടുത്തുള്ള `Compare & pull request` ബട്ടൺ നിങ്ങൾ കാണും. ആ ബട്ടണിൽ ക്ലിക്ക് ചെയ്യുക.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
ഇപ്പോൾ പുൾ റിക്വസ്റ്റ് സമർപ്പിക്കുക.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
ഉടൻ തന്നെ നിങ്ങളുടെ എല്ലാ മാറ്റങ്ങളും ഈ പ്രോജക്റ്റിന്റെ മാസ്റ്റർ ബ്രാഞ്ചിലേക്ക് ഞാൻ ലയിപ്പിക്കും. മാറ്റങ്ങൾ ലയിച്ചുകഴിഞ്ഞാൽ നിങ്ങൾക്ക് ഒരു അറിയിപ്പ് ഇമെയിൽ ലഭിക്കും.
## ഇവിടെ നിന്ന് എങ്ങോട്ട് പോകണം?
അഭിനന്ദനങ്ങൾ! ഒരു സംഭാവകൻ എന്ന നിലയിൽ നിങ്ങൾ പലപ്പോഴും അഭിമുഖീകരിക്കുന്ന സ്റ്റാൻഡേർഡ് _fork -> clone -> edit -> PR_ വർക്ക്ഫ്ലോ നിങ്ങൾ ഇപ്പോൾ പൂർത്തിയാക്കി!
[വെബ് ആപ്പ്](https://firstcontributions.github.io#social-share) എന്നതിലേക്ക് പോയി നിങ്ങളുടെ സംഭാവനകൾ ആഘോഷിക്കുകയും സുഹൃത്തുക്കളുമായും പിന്തുടരുന്നവരുമായും അത് പങ്കിടുകയും ചെയ്യുക.
നിങ്ങൾക്ക് എന്തെങ്കിലും സഹായം ആവശ്യമുണ്ടെങ്കിൽ അല്ലെങ്കിൽ എന്തെങ്കിലും ചോദ്യങ്ങൾ ഉണ്ടെങ്കിൽ ഞങ്ങളുടെ സ്ലാക്ക് ടീമിൽ ചേരാം. [സ്ലാക്ക് ടീമിൽ ചേരുക](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [അധിക മെറ്റീരിയൽ](../additional-material/git_workflow_scenarios/additional-material.md)
## മറ്റ് ടൂളുകൾ ഉപയോഗിച്ചുള്ള ട്യൂട്ടോറിയലുകൾ
[പ്രധാന പേജിലേക്ക് മടങ്ങുക](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-windows-vs-code-tutorial.pt_br.md
+117
View File
@@ -0,0 +1,117 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
É difícil. É sempre difícil a primeira vez que você faz algo. Especialmente quando você está colaborando, cometer erros não é uma coisa confortável. Mas o código aberto tem tudo a ver com colaboração e trabalho em conjunto. Queríamos simplificar a maneira como os novos colaboradores de código aberto aprendem e contribuem pela primeira vez.
Ler artigos e assistir a tutoriais pode ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada. Este projeto visa fornecer orientação e simplificar a maneira como os novatos fazem sua primeira contribuição. Lembre-se, quanto mais relaxado você estiver, melhor você aprenderá. Se você está procurando fazer sua primeira contribuição, basta seguir os passos simples abaixo. Nós prometemos a você, vai ser divertido.
Se você não tiver o Visual Studio Code em sua máquina, [instale-o](https://code.visualstudio.com/download).
**Atenção:** Este tutorial foi feito usando o Visual Studio Code (Versão 1.27.2) em uma máquina Windows 10. Mais adiante neste tutorial, usaremos alguns atalhos de teclado. Eles podem diferir em outros sistemas operacionais (macOS/Linux), bem como no idioma do teclado (UK, DE, etc). Você pode percorrer sua lista de atalhos pesquisando "atalho" na Paleta de Comandos.
## Fork este repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Fork este repositório clicando no botão fork no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub.
O GitHub acompanha o relacionamento entre seu repositório e aquele do qual você o bifurcou. Você pode pensar em seu repositório como uma cópia de trabalho.
A maioria dos repositórios de alto nível do GitHub (ou seja, aqueles que não são bifurcados de nenhum outro repositório) têm uma pequena equipe principal de pessoas que podem confirmar alterações diretamente. Todos os outros contribuidores devem bifurcar o repositório e fazer alterações na bifurcação e, em seguida, criar uma solicitação de pull para solicitar que suas alterações sejam mescladas novamente no repositório de nível superior. Se o administrador de repo de nível superior gostar das alterações, elas serão mescladas e você ganhará fama e fortuna instantâneas! Mais sobre como fazer isso mais tarde.
## Clone seu repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
A próxima etapa é clonar seu repositório para sua máquina para que você possa começar a fazer alterações. O VS Code precisa do URL do seu repositório, então clique no botão "clone" e depois clique no ícone "copiar para a área de transferência".
**CUIDADO:** Um erro que os novos contribuidores costumam cometer é clonar o repositório que você bifurcou _de_ em vez de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de estar clonando seu repositório.
Agora abra o Visual Studio Code. A página de boas-vindas do VS Code aparecerá. A partir daí, pressione `F1` para abrir a barra mostrada abaixo. Observe que já existe um sinal `>` (maior que) no campo de texto. Você também pode acessar o prompt de entrada pressionando `CTRL-P` e digite o caractere `>`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Você pode notar que já existem alguns comandos obscuros listados abaixo. Esses são meus comandos usados recentemente. Então, simplesmente não se importe com eles.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Agora digite `git clone`, apenas `git` ou `clone` (funciona como uma pesquisa).
Selecione a entrada `Git: Clone` e pressione `Entrar`
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Colar URL do repositório" />
Cole a URL do seu repositório e pressione `Entrar`. Isso abrirá um File Explorer onde você pode escolher onde o repositório Git deve ser armazenado.
**Importante**: Certifique-se de que é o repositório bifurcado e não o original, caso contrário não funcionará.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Você deve ver um pop-up de status no canto inferior direito do Visual Studio Code. Depois de terminar, você pode abrir o repositório clonado (agora uma pasta em sua máquina) usando os botões da caixa de diálogo.
## Criar uma branch
Abra a paleta de comandos novamente pressionando `F1`. Digite `branch` e selecione o comando `criar branch` a partir daí. Na próxima etapa digite o nome do seu novo branch, por exemplo `add-david-kroell`. Pressione enter e a ramificação será criada. A filial também já foi verificada. [O que significa checkout?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Faça as alterações necessárias
Abra `Contributors.md` e adicione seu nome em qualquer lugar do arquivo. Este arquivo contém GFM (GitHub Flavored Markdown), que é um sabor proprietário da sintaxe <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Copie um dos outros contribuidores&apos; linhas e modifique-o com seu nome para ter certeza de obter a sintaxe correta - pode ser exigente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Confirmar e enviar alterações para o GitHub
No lado esquerdo do VS Code há um menu com 5 ícones exibidos. Selecione o ícone de controle de versão/Controle de origem.
(Atalho: Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commitar alterações" />
O explorador de arquivos exibe todos os arquivos que foram alterados após o último commit. Ao passar o mouse sobre os arquivos e clicar em `+` (mais), os arquivos são encenados.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Arquivos guardados">
Digite algo na linha na parte superior do explorer e pressione a marca de seleção. As alterações agora estão confirmadas em sua cópia local. Agora as alterações precisam ser enviadas de volta ao GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Arquivos guardados">
Use o ícone de três pontos para abrir o menu onde você seleciona a opção `Publicar Branch`. Isso deve abrir uma caixa de diálogo para colocar suas credenciais do GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Arquivos guardados">
## Envie suas alterações para revisão
Neste ponto, você concluiu sua alteração, mas ela ainda reside apenas em seu repositório. Esta etapa mostrará como enviar uma solicitação ao administrador do repositório de nível superior para mesclar sua alteração.
Em seu repositório no GitHub, você verá o botão `Comparar & pull request` ao lado da nova notificação de branch. Clique nesse botão.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="crie uma pull request" />
Agora envie a solicitação PR - pull request.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Em breve estarei mesclando todas as suas alterações no branch master deste projeto. Você receberá um e-mail de notificação assim que as alterações forem mescladas.
## Para onde ir a partir daqui?
Parabéns! Você acabou de concluir o fluxo de trabalho padrão _fork -> clone -> editar -> PR_ que você encontrará frequentemente como colaborador!
Comemore sua contribuição e compartilhe com seus amigos e seguidores acessando [aplicativo da web](https://firstcontributions.github.io#social-share).
Você pode se juntar à nossa equipe do slack caso precise de ajuda ou tenha alguma dúvida. [Junte-se à equipe do Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material adicional](../additional-material/translations/additional-material.pt_br.md)
## Tutoriais usando outras ferramentas
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_id.md
+121
View File
@@ -0,0 +1,121 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Kontribusi Pertama
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
Sulit. Memang selalu sulit melakukan sesuatu untuk pertama kali. Khususnya ketika kamu berkolaborasi, membuat sebuah masalah bukanlah hal yang mengenakkan. Tetapi proyek terbuka
berarti kolaborasi dan kerjasama. Kami ingin menyederhanakan cara belajar bagi kontributor dan cara berkontribusi untuk pertama kali.
Membaca artikel & menonton tutorial bisa membantu, tetapi lebih baik praktek langsung tanpa membuat masalah apapun pada proyek. Laman ini bertujuan untuk memberikan panduan & menyederhanakan cara bagi pemula untuk membuat kontribusi pertama. Ingat semakin santai kamu, maka semakin baik kamu belajar. Jika kamu ingin membuat kontribusi pertama, cukup ikuti langkah-langkah sederhana di bawah ini. Kami janji, ini akan menyenangkan kok.
Jika kamu belum punya Visual Studio Code pada perangkat mu, [install disini](https://code.visualstudio.com/download).
**Perlu Diingat:** Tutorial ini dibuat menggunakan Visual Studio Code (Versi 1.27.2) pada Windows 10. Nanti dalam tutorial ini kita akan menggunakan beberapa shortcut keyboard. Ini mungkin berbeda pada sistem operasi lain (macOS/Linux) serta bahasa keyboard (UK, DE, dll). Kamu dapat menelusuri daftar pintasan mu dengan mencari "shortcut" di Palet Perintah.
## Fork repositori ini
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Fork repo ini dengan mengklik tombol fork di kanan atas halaman ini. Ini akan membuat salinan repositori ini di akun GitHub Anda.
GitHub selalu menjaga repo mu dan sumber repo yang sudah kamu fork supaya tetap pada jalurnya. Kamu bisa menganggap repo mu sebagai salinan pekerjaan.
Sebagian besar repo GitHub tingkat atas (yaitu yang tidak di-copy dari repo lain mana pun) mempunyai tim inti yang terdiri dari orang-orang yang dapat langsung melakukan perubahan. Semua kontributor lain harus melakukan fork repo dan membuat perubahan pada fork, lalu membuat Pull Request untuk meminta perubahan mereka digabungkan kembali ke repo tingkat atas. Jika administrator repo tingkat atas menyukai perubahan, mereka akan menggabungkan perubahan mu dan kamu bisa mendapatkan reputasi dan nasib baik! Lebih lanjut tentang cara melakukannya akan dibahas nanti.
## Klon Repositori mu
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
Langkah selanjutnya adalah mengkloning repo mu ke perangkat mu sehingga bisa segera mulai membuat perubahan. VS Code membutuhkan URL repo mu agar terhubung, jadi klik tombol "clone" dan kemudian klik ikon "copy to clipboard".
**HATI-HATI:** Satu kesalahan yang sering dilakukan oleh kontributor baru adalah mengkloning repo utama yang kamu fork _sumbernya_ daripada mengkloning repo mu sendiri. Periksa alamat browser mu dan pastikan kamu mengkloning repo mu sendiri.
Sekarang buka Visual Studio Code. Halaman selamat datang dari VS Code akan muncul. Dari sana tekan `F1` untuk membuka bar yang ditunjukkan di bawah ini. Perhatikan bahwa sudah ada tanda `>` (lebih besar dari) di kolom teks. Anda juga dapat membuka input prompt dengan menekan `CTRL-P` lalu ketik `>`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Anda mungkin memperhatikan bahwa sudah ada beberapa perintah tidak jelas yang tercantum di bawah ini. Itu adalah perintah yang digunakan baru-baru ini. Jadi, hiraukan saja.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Sekarang ketik `git clone`, hanya `git` atau `clone` (berfungsi seperti melakukan pencarian).
Pilih Entri `Git: Clone` dan tekan `Enter`
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
Tempelkan URL repositori kamu dan tekan `Enter`. Ini akan membuka File Explorer di mana kamu dapat memilih di mana repositori Git harus disimpan
**Penting**: Pastikan itu adalah repositori yang kamu fork dan bukan yang asli, jika tidak maka tidak akan berfungsi
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Kamu akan melihat status popup di kanan bawah Visual Studio Code. Setelah selesai, kamu dapat membuka repositori kloning (di folder yang sudah kamu pilih) menggunakan tombol di dialog.
## Membuat Cabang (Branch)
Buka kembali palet perintah dengan menekan `F1`. Ketik `branch` dan pilih perintah `create branch` dari sana. Pada langkah berikutnya ketik nama cabang baru kamu, misalnya `add-david-kroell`. Tekan enter dan cabang akan dibuat. Cabang juga sudah siap dipakai. [Apa artinya checkout?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Buat Perubahan yang diperlukan
Buka `Contributors.md` dan tambahkan nama kamu di mana saja di file. File ini berisi GFM (GitHub Flavoured Markdown) yang merupakan ciri khas sintaks <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Salin salah satu kontributor lain&apos; baris dan modifikasi dengan nama mu untuk memastikan kamu menggunakan sintaks yang benar - itu bisa pilih-pilih
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Commit & Push perubahan ke GitHub
Di sisi kiri VS Code adalah menu dengan 5 ikon yang ditampilkan. Pilih ikon versi kontrol/Sumber Kontrol.
(Pintasan: Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
File explorer menampilkan semua file yang diubah setelah komit terakhir. Dengan mengarahkan penunjuk pada file dan mengklik `+` (plus) file akan disiapkan.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
Ketik sesuatu pada baris di atas explorer dan tekan tanda centang. Perubahan telah tersimpan pada salinan lokal kamu. Sekarang perubahan harus di _push_ kembali ke GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
Gunakan ikon titik tiga untuk membuka menu tempat kamu akan memilih opsi `Publish Branch`. Ini akan membuka dialog untuk memasukkan kredensial GitHub kamu.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## Submit perubahan mu untuk diperiksa
Dititik ini kamu telah menyelesaikan perubahan mu tetapi masih berada di repo mu sendiri. Langkah ini akan menunjukkan bagaimana cara mengirimkan permintaan ke administrator repo tingkat atas untuk menggabungkan perubahan
Pada repo mu di GitHub, kamu akan melihat tombol `Compare & pull request` di sebelah pemberitahuan cabang baru. Klik tombol itu.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Sekarang kirimkan permintaan _pull_.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Segera saya akan menggabungkan semua perubahan mu ke dalam cabang utama proyek ini. Kamu akan mendapatkan email pemberitahuan setelah perubahan digabungkan.
## Kemana lagi setelah ini?
Selamat! kamu baru saja menyelesaikan alur kerja _fork -> clone -> edit -> PR_ standar yang akan sering kamu temui sebagai kontributor!
Rayakan kontribusi mu dan bagikan dengan teman dan pengikut kamu dengan membuka [web app](https://firstcontributions.github.io#social-share).
Kamu dapat bergabung dengan tim slack kami jika memerlukan bantuan atau memiliki pertanyaan. [Bergabung dengan tim Slack](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
### [ Materi tambahan ](../../additional-material/translations/additional-material.id.md)
## Tutorial menggunakan Alat lain
[Kembali ke halaman utama](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_pt_br.md
+124
View File
@@ -0,0 +1,124 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
É difícil, sempre é difícil quando fazemos alguma coisa pela primeira vez. Especialmente quando você está colaborando, cometendo erros, não é nada confortável. No entanto, o open source é totalmente sobre colaboração e trabalho em equipe. Por isso, nós queremos simplificar a maneira como os novos colaboradores de código aberto aprendem e contribuem pela primeira vez.
Ler artigos e assistir a tutoriais até podem ajudar, mas o que é melhor do que fazer as coisas sem bagunçar nada. Este projeto tem como objetivo orientar & simplificar a forma como os iniciantes fazem a sua primeira contribuição. Lembre-se que você aprende melhor quando está relaxado. Se você deseja fazer sua primeira contribuição, basta seguir os passos abaixo. Nós prometemos a você que será divertido!
Se você não tem o Visual Studio 2017 na sua máquina, [instale-o](https://code.visualstudio.com/download).
**Nota:** Este tutorial foi feito utilizando o Visual Studio Code (Versão 1.27.2) no Windows 10. Mais tarde, neste tutorial, vamos utilizar alguns atalhos no teclado. Eles podem ser diferentes em outros sistemas operacionais (mac/OS/Linux) assim como em teclados de outras linguagens (UK, DE, etc). Você pode pesquisar na lista de atalhos, buscando por "atalhos" na Paleta de Comando.
## Faça o *Fork* deste repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Faça um *fork* deste repositório clicando no botão *fork* (bifurcar) no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub.
O GitHub rastreia a relação entre seu repositório e o original, o qual você fez o *fork*. Você pode pensar em seu repositório como uma cópia de trabalho.
Muitos dos repositórios matrizes do GitHub (ou seja, aqueles que não são *Fork* de nenhum outro repositório) tem um pequeno grupo de pessoas que podem fazer commits de modificações diretamente. Todos os outros contribuidores devem fazer um *fork* do repositório e fazer alterações no *fork*, em seguida, devem criar um Pull Request para solicitar um *Merge* (mesclagem) das modificações feitas no repositório original.
Se um dos administradores do repositório gostar e aprovar as tuas mudanças, eles *mergearão* e você ganhará fama e fortuna imediatamente! Abaixo, há mais detalhes sobre como fazer isso.
## Clone o seu repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard".
**CUIDADO:** Um erro que os novatos cometem com frequência é clonar o repositório do qual você fez o fork, ao invés de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório.
Agora, abra o Visual Studio Code. A página principal do VS Code vai minimizar. A partir daí, pressione `F1` para abrir a barra mostrada abaixo. Perceba que já existe um `>` (maior que) no campo de texto. Você pode também chegar até o prompt de entrada pressionando `CTRL-P` e então inserindo o caracter `>`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Você pode notar que já aí já existem alguns comandos de sugestão abaixo. Esses são os seus comandos utilizados recentemente. Então, apenas ignore-os.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Agora, digite `git clone`, apenas `git` ou `clone` (isso funcionará como uma pesquisa).
Selecione a opção `Git: Clone` e então aperte `Enter`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
Cole a URL do seu repositório e aperte `Enter`. Isso vai abrir o Explorador de Arquivo onde você pode escolher onde o repositório Git será armazenado.
**Importante**: Tenha certerza que este é o repositório *forkeado* e não é o original. Se não, não funcionará.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Você pode ver uma janela do status no canto inferior direito do Visual Studio Code. Depois de finalizado esse processo, você pode abrir o repositório clonado (agora, uma pasta na sua máquina) e usar os botões no diálogo.
## Crie uma *branch*
Abra a Paleta de Comando novamente, pressionando `F1`. Digite nele `branch` e selecione o comando `create branch` a partir das sugestões. No próximo passo, digite o nome da sua nova *branch*, por exemplo: `add-david-kroell`. Presione `Enter` e a *branch* será criada. A *branch* também está preparada para o *check out*. [*O que isso significa?*](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Faça as mudanças necessárias
Abra o arquivo `Contributors.md` e adicione o seu nome no fim da lista. Esse arquivo contém GFM (GitHub Flavored Markdown), que é uma função nativa da sintaxe do <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Copie uma das outras linhas dos contribuidores e modifique-a com o seu nome. Tenha certeza que a sintaxe está correta - ela pode ser exigente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Faça um *Commit* & um *Push* das suas mudanças para o GitHub
No lado esquerdo do VS Code tem um menu com 5 ícones a amostra. Selecione o ícone de `Controle de Versão/Controle da Fonte`.
(Atalho : Ctrl + Shift + G)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
O Explorador de arquivos mostra todos os arquivos que foram mudados depois do último commit. Sobrepondo o mouse nos arquivos e clicando no `+` (mais) os arquivos serão colocados no *stage*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
Escreva algo na caixa de texto, no topo do explorador e pressione o botão de *check*. As mudanças agora foram *commitadas* para a sua cópia local. Agora, as mudanças tem que serem mandadas para o GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
Use o ícone dos três pontos para abrir o menu onde você selecionará a opção `Publicar Branch`. Isso deve abrir uma caixa de diálogo para colocar as tuas credenciais do GitHub.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## Submeta suas mudanças para uma revisão
Nesse ponto, você completou suas mudanças, mas elas ainda estão no seu repositório. Esse passo vai mostrar para você como submeter uma requisição para o administrador do repositório original para *mergear* suas mudanças.
No seu repositório no GitHub você verá o botão `Compare & Pull request` próximo a notificação da branch. Clique nesse botão.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Agora, submeta o *pull request*.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Breve as suas mudanças serão *mergeadas* na branch `master` desse projeto. Você será notificado por email uma vez que as mudanças forem *mergeadas*.
## Para onde ir ?
Parabéns! Você acabou de completar o fluxo de trabalho *fork -> clone -> edit -> PR* que vocẽ vai realizar frequentemente como um contribuidor!
Celebre a sua contribuição e compartilhe-a com os seus amigos e seguidores indo para o [web app](https://firstcontributions.github.io#social-share).
Você pode se juntar à nossa comunidade no slack, caso precise de alguma ajuda ou tenha alguma dúvida.
[Faça parte da nossa comunidade no Slack!](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY)
### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriais utilizando outras ferramentas
[Retorne para a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md)
docs/gui-tool-tutorials/translations/github-windows-vs2017-tutorial.pt_br.md
+149
View File
@@ -0,0 +1,149 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
|<img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/61/Visual_Studio_2017_logo_and_wordmark.svg/2000px-Visual_Studio_2017_logo_and_wordmark.svg.png" width="200">|Visual Studio 2017 Edition|
|---|---|
É difícil. Sempre é difícil fazer algo pela primeira vez. Especialmente quando você está colaborando, cometer erros não é confortável. Mas o open sourece tem tudo a ver com colaboração e trabalho em equipe. Nós queremos simplificar a maneira de aprendizagem aos novos contribuidores de open source e ajudar em sua primeira contribuição.
Lendo artigos e olhando tutoriais podem ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada.
Esse projeto visa em providenciar uma orientação e simplificar a maneira dos novatos a conseguirem a sua primeira contribuição.
Lembre-se, quanto mais relaxado melhor será o aprendizado. Se você está procurando em fazer a sua primeira contribuição, siga esses passos abaixo. Nós prometemos a você que vai ser divertido.
Se você não possui o Visual Studio 2017 na sua máquina, [instale-o aqui](https://www.visualstudio.com/downloads/).
## Faça um Fork deste repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/fork.png" alt="fork this repository" />
Para fazer um Fork deste repositório, basta clicar no botão de fork no topo da página. Isso criará uma cópia do repositório na
sua conta GitHub.
O GitHub acompapanhará o seu Fork e o repositório principal. Em outras palavras, podemos afirmar que o seu Fork é uma cópia do repositório principal.
Os respositórios de mais alto nível do GitHub (exemplo: aqueles que não há um fork de nenhum outro repositório), tem uma pequena equipe principal de pessoas que podem diretamente fazer os seus commits. Os outros contribuidores deverão criar um Fork do respositório e fazer as mudanças nesse Fork, em seguida criar um Pull Request perguntando se essas mudanças poderão ser mescladas no repositório de alto nível. Se o administrador do repositório gostar das alterações ele irá mesclar as modificações e você ganhará instantaneamente fama e fortuna! Abaixo há um tutorial de como realizar.
## Clone o seu repositório
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/clone.png" alt="clone this repository" />
O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard".
**CUIDADO:** Um erro que os novatos cometem com frequência é clonar o repositório do qual você fez o fork, ao invés de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório.
Agora é a hora de ir para o Visual Studio 2017! Você estará trabalhando na aba *Team Explorer* na maior parte do tutorial. Se ela não estiver aberta por padrão, clique em `View > Team Explorer` para abrí-la.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-01-clone1.png" alt="Team Explorer" />
*Team Explorer* tem muitas áreas e muitos botões de navegação, localizados no topo para te ajudar a achar essas diferentes áreas. Para clonar o repositório, você vai precisar estar na *Connect view*, que deve ser a padrão. Se você não conseguir ver o botão *clone*, clique no botão verde, em formato de tomada, no topo.
Click the `Clone` option under **Local Git Repositories** and paste the URL to your repo in the text box. This should be the URL you copied to your clipboard from GitHub previously.
Clique na opção `Clone` abaixo de **Local Git Repositories** e cole a URL do seu repositório na caixa de texto. Essa URL tem que ser a mesma que você copiou no GitHub anteriormente.
Clique no botão `Clone` para iniciar o processo.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-02-clone2.png" alt="Clone repo" />
Quando o processo estiver completo, você será movido para a aba *Solution Explorer*, onde você poderá ver o conteúdo do repositório clonado. O seu parecerá um pouco diferente da foto abaixo, por que os arquivos estão em constante mudança!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-03-clone3.png" alt="Solution Explorer" />
## Crie uma *branch*
Clique de volta na aba *Team Explorer* e use o a seleção principal de navegação para mostrar as *Branchs* disponíveis.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-04-branch1.png" alt="Branches view" />
Você deve ver o repositório **first-contributions** e a branch padrão, que é chamada `main`. Clique com o botão direito na `main` e escolha `New Local Branch From...`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-05-branch2.png" alt="New branch" />
Dê à sua branch um nome como `add-<seu_nome_aqui>` por exemplo: `add-alonzo-church`.
Deixe a caixa de seleção `Checkout branch` marcada e clique no botão `Create Branch`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-06-branch3.png" alt="Create branch" />
Você deverá ver a sua branch nova na lista.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-07-branch4.png" alt="See new branch" />
## Faça as mudanças necessárias
Abra o arquivo `Contributors.md` e adicione o seu nome no fim da lista. Esse arquivo contém GFM (GitHub Flavored Markdown), que é uma função nativa da sintaxe do <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a>.
Copie uma das outras linhas dos contribuidores e modifique-a com o seu nome. Tenha certeza que a sintaxe está correta - ela pode ser exigente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-08-change1.png" alt="Add your name" />
## Commit & Push changes to GitHub
Volte para a aba *Team Explorer* e navegue para a aba *Changes*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-09-commit1.png" alt="Changes" />
Coloque a informação que você queira, poste o seu *commit* e clique em `Save`. O Visual Studio relembrará isso para futuros *commits*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-10-commit2.png" alt="Git user information" />
**NOTA:** Visual Studio usa uma pasta escondida, chamada `.vs` para salvar suas configurações e preferências pessoais. O conteúdo desta pasta **não deverá ser salvo no Git**.
Se ela não estiver sido ingnorada ainda, você deve informar ao Git para ignorar essa pasta, com o intuito dela não ser mandada para o repositório.
Essa pasta já foi ignorada neste repositório, então você não tem que realizar este passo. Ele está aqui somente para você ter uma referência para projetos futuros.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-11-commit3.png" alt="Ignore vs folder" />
Agora você deve ver uma lista de arquivos modificados e uma caixa de texto para digitar um cometário do *commit*. Os comentários devem ser breves, mas concretos. Não tem nada pior do que ler um comentário de um *commit* e ver algo como: `"Eu atualizei algumas coisas"`. Tire alguns segundos para realizar o seu *commit*. O seu time vai agradecer bastante mais tarde e você pode até agradecer a você mesmo!
Clique em `Commit All and Push` para realizar um *commit* local e fazer um *push* das suas mudanças para o seu repositório, tudo em um único passo.
**NOTA:** Um *Commit* pode ser realizado separadamente de um *Push*. Fazemos os dois juntos por conveniência. As mudanças realizadas e salvas em *commits* locais não serão refletidos no teu repositório no GitHub até que você faça um *Push*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-12-commit4.png" alt="Commit and Push" />
A primeira vez que você realizar um *Push* para o GitHub, Visual Studio solicitará as suas credenciais do GitHub. Depois disso, ele as guardará no *cache*, para que você não precise realizar isso frequentemente.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-13-commit5.png" alt="Login" />
Depois de realizar uma operação de *Push*, abra o seu repositório no GitHub e deverá ver uma mensagem indicando um *push* recente de uma *branch*.
Você pode ver suas mudanças abrindo a seleção `Branch: main` e selecionando a sua `branch`. Parabéns! Você pode compartilhar a URL da `branch` com o mundo e mostrar o seu progresso!
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-14-commit6.png" alt="View pushed branch on GitHub" />
## Submeta as suas mudanças para uma revisão
Neste ponto, você completou as mudanças, mas elas ainda estão somente no seu repositório. Esse passo te mostrará como submeter essas mudanças para um administrador para que ele possa fazer um *merge* das tuas mudanças.
No seu repositório no GitHub, você verá o botão `Compare & pull request` próximo à notificação da *branch*. Cloque nesse botão.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/compare-and-pull.png" alt="create a pull request" />
Agora submeta o *Pull Request*.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/submit-pull-request.png" alt="submit pull request" />
Assim que possível, essas mudanças serão *mergeadas* para a `main branch` deste projeto. Você será notificado via email, quando essa movimentação for realizada.
## Para onde ir daqui?
Parabéns! Você acabou de completar o fluxo de trabalho *fork -> clone -> edit -> PR* que vocẽ vai realizar frequentemente como um contribuidor!
Celebre a sua contribuição e compartilhe-a com os seus amigos e seguidores indo para o [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).
Você pode se juntar à nossa comunidade no slack, caso precise de alguma ajuda ou tenha alguma dúvida.
[Faça parte da nossa comunidade no Slack!](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY)
### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriais utilizando outras ferramentas
[Retorne para a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md)
docs/gui-tool-tutorials/translations/gitkraken-tutorial-es.md
+116
View File
@@ -0,0 +1,116 @@
[![Amor por el Código Abierto](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Licencia: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Ayudantes de Código Abierto](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeras Contribuciones
|<img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="200">|GitKraken Edition|
|---|---|
Es difícil. Siempre es difícil cuando se hace algo por primera vez. Especialmente cuando se colabora, cometer errores no es algo agradable. Pero el código abierto trata sobre la colaboración y el trabajo en conjunto. Queríamos simplificar la manera en que los contribuyentes de código abierto aprenden y contribuyen por primera vez.
Leer artículos y ver tutoriales puede ayudar, pero ¿qué es mejor que hacer las cosas sin estropear nada?. Este proyecto tiene como objetivo proporcionar orientación y simplificar la manera en que los novatos hacen su primera contribución. Recuerda que cuando más relajado estés, mejor aprenderás. Si buscas hacer tu primera contribución sólo sigue los simples pasos a continuación. Te lo prometemos, será divertido.
## Git Kraken
Descarga [GitKraken](https://www.gitkraken.com), Instálalo y ábrelo.
Deberías ver el diálogo modal "Welcome to GitKraken" - Regístrate con Github y permite el acceso a Gitkraken a tu cuenta de GitHub.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(opcional) Dirígete a File -> Preferences y configura el directorio de tu proyecto en la raíz de tus repositorios locales.
## Bifurca (Fork) este repositorio
Bifurca este repositorio clickeando en el botón fork en la parte superior derecha de esta página.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="fork this repository" />
Esto creará una copia de este repositorio en su cuenta.
## Clona el repositorio
En GitKraken, ve a File -> Clone Repo.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
Selecciona GitHub.com en el panel derecho. Bajo tu nombre de usuario, deberías ver first-contributions. Haz click en ese repositorio y verifica la ruta completa mostrada al final del panel.
Una vez estés satisfecho con la ruta, clickea "Clone the repo!".
## Crear una rama (*branch*)
Clickea el botón *branch* de la barra de herramientas.
Nombra tu rama "add-your-name", por ejemplo: "add-william-sutton"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## Haz los cambios necesarios y confirma (*Commit*) esos cambios
Ahora abre el archivo `Contributors.md` en un editor de texto y agrégale tu nombre, luego guarda el archivo.
Si tienes el repositorio abierto en GitKraken deberías ver que hay cambios. Revisa y prepara esos cambios seleccionando la confirmación (*commit*) más reciente marcada con "// WIP" y el número de archivos cambiados y el tipo de cambio.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
Revisa los archivos que han sido cambiados y decide cuáles deseas preparar para confirmar (*stage*). La preparación es importante para decirle a git exactamente que archivos deseas asociar con esta confirmación (*commit*).
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
Una vez tengas un buen mensaje de confirmación (*commit*) ("Add <your-name> to Contributors list" suena agradable y descriptivo) y estés feliz con tus cambios, puedes clickear "Stage all changes" para preparar todo lo modificado o "Stage File" para preparar un archivo individual.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
Si cambias de idea, puedes olvidar (*unstage*) esos cambios, o puedes descartárlos todos.
ADVERTENCIA: Como lo implica la palabra descartar, esta es una operación destructiva. Hazlo solo si no quieres ningún cambio(s) desde cualquier repositorio en el que te encuentres.
Clickea en *commit*.
Felicidades, has confirmado (*committed*) todos los cambios a la copia local de la rama de tu bifurcación (*fork*) de first-contributions.¡Adelante!.
## Sube (*push*) los cambios a GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
Haz click en el botón *Push* en la barra de herramientas.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
Envía los cambios en la rama origen si quieres que los cambios se reflejen en la rama maestra directamente, sino selecciona la rama apropiada a la cual quieres hacer el push.
## Envía tus cambios para revisión
Si vas a tu repositorio en github, verás el botón `Compare & pull request`. Haz click en él.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
Ahora confirma el pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit pull request" />
Pronto estaré fusionando todos sus cambios en la rama master de este proyecto. Recibirás una notificación por correo electrónico cuando los cambios hayan sido fusionados.
## ¿Cuáles son los siguientes pasos?
¡Enhorabuena! ¡Has completado el flujo de trabajo _fork -> clone -> edit -> PR_ que encontrarás habitualmente como contribuidor!
Celebra tu contribución y compártela con tus amigos y seguidores yendo a [App web](https://firstcontributions.github.io/#social-share).
También podrías unirte a nuestro equipo de Slack en caso de que necesites ayuda o tengas alguna pregunta. [Únete a nuestro equipo de Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriales con otras herramientas
[Regresar a la página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/gitkraken-tutorial-fr.md
+120
View File
@@ -0,0 +1,120 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Première Contribution
|<img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="200">|GitKraken Edition|
|---|---|
C'est difficile. C'est toujours difficile, quand on fait quelque chose pour la première fois. Surtout lorsque vous collaborez, faire des erreurs n'est pas une chose confortable. Mais l'open source concerne avant tout la collaboration et le travail en équipe.
Nous voulions simplifier la manière dont les nouveaux contributeurs open source apprennent et contribuent pour la première fois.
Lire des articles et regarder des tutoriels peut aider, mais quoi de mieux que de vraiment faire les choses sans tout gâcher. Ce projet vise à fournir des conseils et à simplifier la manière dont les novices font leur première contribution.
Rappelez-vous, plus vous êtes détendu, mieux vous apprenez. Si vous cherchez à faire votre première contribution, suivez simplement les étapes simples ci-dessous. Nous vous promettons que ce sera amusant
## Git Kraken
Télécharger [GitKraken](https://www.gitkraken.com), Installer et l'ouvrir.
Vous devriez lire "Welcome to GitKraken" - Enregistrer vous via Github en cliquant sur "Sign in with GitHub" et autoriser GitKraken à accéder à votre compte GitHub account.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(optionnel) Allez dans Fichier (File) -> Préférences (Preferences) et définissez votre répertoire de projet à la racine de vos dépôts locaux.
## Forker ce dépôt
Forker ce dépôt en cliquant sur le bouton Fork en haut de cette page.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="dupliquez ce dépôt" />
Cela créera une copie de ce dépôt dans votre compte.
## Cloner le dépôt
Dans GitKraken, aller à File -> Clone Repo.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
Selectionner GitHub.com dans le panneau de droite. Sous votre username, vous devriez voir first-contributions apparaître. Cliquer sur ce dépôt et vérifier le chemin complet vers le dossier en bas du panneau d'affichage.
Une fois que vous êtes satisfait du chemin, cliquez sur "Clone the repo!".
## Créer une branche
Cliquez sur le bouton "branche" dans la barre d'outils.
Nommez votre branche "add-your-name", par exemple : "add-william-sutton".
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## Effectuez et validez des modifications.
Ouvrez maintenant le fichier Contributors.md dans un éditeur de texte et ajoutez-y votre nom, puis enregistrez le fichier.
Si vous avez le dépôt ouvert dans GitKraken, vous verrez qu'il y a des modifications. Examinez et mettez en scène ces modifications en sélectionnant le dernier commit marqué par "// WIP" et le nombre de fichiers modifiés ainsi que le type de modification.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
Examinez les fichiers qui ont été modifiés et décidez de ceux que vous souhaitez "stage". "Staging" est important pour indiquer à git exactement quelles modifications de fichier vous souhaitez associer à ce commit.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
Once you have a good commit message ("Add <your-name> 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.
Lorsque vous avez un bon message de commit ("Add <your-name> to Contributors list" semble joli et descriptif) et que vous êtes satisfait de vos modifications,
vous pouvez cliquer sur "Stage all changes" pour "stage" tout ce qui est modifié ou "Stage File" pour ajouter un fichier individuel.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
Si vous changez d'avis, vous pouvez "unstage" ces modifications, ou vous pouvez les supprimer complètement.
ATTENTION : Comme le mot supprimer l'indique, c'est une opération destructrice. Faites-le seulement si vous ne voulez aucune modification(s) du dépôt dans lequel vous vous trouvez.
Appuyez sur "commit".
Félicitations, vous avez validé toutes les modifications dans votre copie locale de votre branche de votre fork de first-contributions. En avant !
## Push changes to GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
Cliquez sur le bouton Push dans la barre d'outils.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
Soumettez les modifications sur la branche origin si vous souhaitez que les modifications se reflètent directement dans la branche master, sinon sélectionnez la branche appropriée que vous souhaitez pousser (push).
## Soumettez vos modifications pour revision (review)
Si vous allez sur votre dépôt sur GitHub, vous verrez le bouton Compare & pull request. Cliquez sur ce bouton.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
Maintenant, soumettez la pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit pull request" />
Bientôt, je fusionnerai toutes vos modifications dans la branche master de ce projet. Vous recevrez un e-mail de notification une fois les modifications fusionnées (merge).
## Que faire ensuite ?
Félicitations ! Vous venez de terminer le workflow standard fork -> clone -> edit -> PR que vous rencontrerez souvent en tant que contributeur !
Célébrez votre contribution et partagez-la avec vos amis et abonnés en vous rendant sur l'application [web](https://firstcontributions.github.io/#social-share).
Vous pouvez rejoindre notre équipe Slack si vous avez besoin d'aide ou si vous avez des questions. [Rejoignez l'équipe Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Autre-Materiel](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriels avec d'autres outils
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/gitkraken-tutorial.pt-br.md
+126
View File
@@ -0,0 +1,126 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeiras Contribuições
|<img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/61/Visual_Studio_2017_logo_and_wordmark.svg/2000px-Visual_Studio_2017_logo_and_wordmark.svg.png" width="200">|Visual Studio 2017 Edition|
|---|---|
É difícil. Sempre é difícil fazer algo pela primeira vez. Especialmente quando você está colaborando, cometer erros não é confortável. Mas o open sourece tem tudo a ver com colaboração e trabalho em equipe. Nós queremos simplificar a maneira de aprendizagem aos novos contribuidores de open source e ajudar em sua primeira contribuição.
Lendo artigos e olhando tutoriais podem ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada.
Esse projeto visa em providenciar uma orientação e simplificar a maneira dos novatos a conseguirem a sua primeira contribuição.
Lembre-se, quanto mais relaxado melhor será o aprendizado. Se você está procurando em fazer a sua primeira contribuição, siga esses passos abaixo. Nós prometemos a você que vai ser divertido.
## Git Kraken
Baixe [GitKraken](https://www.gitkraken.com), Instale e abra.
Provavelmente aparecerá um "Bem-vindo ao GitKraken" com um espaço para entrar na sua conta do GitHub e permitir que o GitKraken possa ter o acesso dela.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-login.png" alt="login to GitHub" />
(opcional) Vá para Aqruivos -> Preferências e ajuste o diretório do seu projeto para a raiz de seus repositórios locais.
## Faça um Fork deste repositório
Para fazer um Fork deste repositório, basta clicar no botão de fork no topo da página.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/fork.png" alt="fork this repository" />
Isso criará uma cópia do repositório na sua conta GitHub.
## Clone o seu repositório
No GitKraken, vá até Arquivo -> Clone Repositório.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-clone.png" alt="clone this repository" />
Selecione GitHub.com no painel direito. De baixo do nome de usuário, deverá aparecer "first-contributions". Clique nesse repositório e confirme na parte inferior do painel, se aparece o local do diretório onde você quer clonar.
Quando estiver tudo certo com o diretório, clique em "Clone o repositório!"
## Crie uma Branch
Clique o botão branch na barra de ferramentas.
Nomeie a sua branch "add-seu-nome", for example: "add-william-sutton"
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-branch.png" alt="name your branch" />
## Faça mudanças necessárias e faça um commit nelas
Agora abra o arquivo `Contributors.md` em um editor de texto e adicione o seu nome, em seguida salve-o.
Se você estiver com o repositório aberto no GitKraken, haverá mudanças.
Revise e faça um Stage nessas mudanças selecionando o commit mais recente marcado com "// WIP" e com número de arquivos modificados e o tipo de mudança.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-edit.png" alt="edit some file(s)" />
Revise esses arquivos que foram modificados e decida o que colocar no Stage. O Stage é importante, pois informa o Git extamente quais arquivos modificados você quer mandar no commit.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-stage.png" alt="stage your changes" />
Quando escrever uma boa mensagem no commit ("Add <seu-nome> para a lista de Contribuidores" parece bom e descritivo) e satisfeito com as suas mudanças, você pode apertar no "Stage todas as mudanças" para fazer o Stage em todas as alterações ou "Stage Arquivo" para cada arquivo modificado individualmente.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-commit.png" alt="clone this repository" />
Se você mudar de ideia, você pode fazer um Unstage (processo reverso do Stage) das sua modificações ou discartar todas elas juntas.
CUIDADO: A palavra discartar fala por si só, ou seja, é uma operação destrutiva. Só faça isso, se você não quer nenhuma mundança no repositório que estiver trabalhando.
Aperte commit.
Parabéns, você acabou de fazer um commit de todas as suas mudanças na sua branch local do seu Fork. Em diante!
## Faça um Push nas suas modificações para o GitHub
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-push.png" alt="push your changes" />
Na barra de ferramentas, clique no botão Push.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-origin.png" alt="origin or branch" />
Se você quer enviar as mudanças direto para branch master, você pode enviar para a branch de origem. Caso contrário, selecione uma branch apropriada para mandar.
## Envie as suas mudanças para revisão
No seu repositório do GitHub você vai ver um botão escrito: `Compare & pull request`, que fica ao lado da notificação da nova branch. Clique nesse botão.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/compare-and-pull.png" alt="create a pull request" />
Agora envie esse Pull Request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/submit-pull-request.png" alt="submit pull request" />
Logo irei mesclar todas as suas mudanças na branch master do projeto. Você receberá uma notificação pelo e-mail quando as alterações forem mescladas.
## Onde eu posso ir a partir daqui?
Parabéns! Você completou o fluxo de trabalho básico _fork -> clone -> edit -> PR_, onde você encontrará muito como contribuidor.
Celebre a sua contribuição e compartilhe com seus amigos e seguidores no [web app](https://firstcontributions.github.io/#social-share).
Caso precise de ajuda ou tenha alguma pergunta, você pode se juntar à nossa equipe Slack. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Material Adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutoriais usando outras ferramentas
[Voltar para página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
docs/gui-tool-tutorials/translations/malayalam/githiub-desktop-tutorial-ml.md
+128
View File
@@ -0,0 +1,128 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# ആദ്യ സംഭാവനകൾ
| <img alt="Git Bash" src="https://cdn.icon-icons.com/icons2/2699/PNG/512/git_scm_logo_icon_170096.png" width="200"> | Git Bash Edition |
| ------------------------------------------------------------------------------------------------------------------ | ---------------- |
ഇത് ബുദ്ധിമുട്ടാണ്. നിങ്ങൾ ആദ്യമായി എന്തെങ്കിലും ചെയ്യുമ്പോൾ എല്ലായ്പ്പോഴും ബുദ്ധിമുട്ടാണ്. പ്രത്യേകിച്ചും നിങ്ങൾ സഹകരിക്കുമ്പോൾ, തെറ്റുകൾ വരുത്തുന്നത് സുഖകരമായ കാര്യമല്ല. എന്നാൽ ഓപ്പൺ സോഴ്‌സ് എന്നത് സഹകരിച്ച് പ്രവർത്തിക്കുന്നതിനും ഒരുമിച്ച് പ്രവർത്തിക്കുന്നതിനുമാണ്. പുതിയ ഓപ്പൺ സോഴ്‌സ് സംഭാവകർ ആദ്യമായി പഠിക്കുകയും സംഭാവന ചെയ്യുകയും ചെയ്യുന്ന രീതി ലളിതമാക്കാൻ ഞങ്ങൾ ആഗ്രഹിക്കുന്നു.
ലേഖനങ്ങൾ വായിക്കുന്നതും ട്യൂട്ടോറിയലുകൾ കാണുന്നതും സഹായിക്കും, എന്നാൽ യാതൊന്നും കുഴപ്പത്തിലാക്കാതെ കാര്യങ്ങൾ ചെയ്യുന്നതിനേക്കാൾ നല്ലത് എന്താണ്. ഈ പ്രോജക്റ്റ് മാർഗ്ഗനിർദ്ദേശം നൽകാനും പുതുമുഖങ്ങൾ അവരുടെ ആദ്യ സംഭാവന നൽകുന്ന രീതി ലളിതമാക്കാനും ലക്ഷ്യമിടുന്നു. നിങ്ങൾ എത്രത്തോളം വിശ്രമിക്കുന്നുവോ അത്രയും നന്നായി പഠിക്കുമെന്ന് ഓർക്കുക. നിങ്ങളുടെ ആദ്യ സംഭാവന നൽകാൻ നിങ്ങൾ ആഗ്രഹിക്കുന്നുവെങ്കിൽ, ചുവടെയുള്ള ലളിതമായ ഘട്ടങ്ങൾ പിന്തുടരുക. ഞങ്ങൾ നിങ്ങൾക്ക് വാഗ്ദാനം ചെയ്യുന്നു, അത് രസകരമായിരിക്കും.
നിങ്ങളുടെ വിൻഡോസ് മെഷീനിൽ ഗീത് ബാഷ് ഇല്ലെങ്കിൽ, [install it](https://git-scm.com/download/win).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
## ഈ ശേഖരം ഫോർക്ക് ചെയ്യുക
ഈ പേജിൻ്റെ മുകളിൽ വലതുവശത്തുള്ള ഫോർക്ക് ബട്ടണിൽ ക്ലിക്കുചെയ്ത് ഈ റിപ്പോ ഫോർക്ക് ചെയ്യുക.
ഇത് നിങ്ങളുടെ അക്കൗണ്ടിൽ ഈ ശേഖരത്തിൻ്റെ ഒരു പകർപ്പ് സൃഷ്ടിക്കും.
## ശേഖരം ക്ലോൺ ചെയ്യുക
ഇപ്പോൾ ഈ റിപ്പോ നിങ്ങളുടെ മെഷീനിലേക്ക് ക്ലോൺ ചെയ്യുക.
പ്രധാനപ്പെട്ടത്: ഒറിജിനൽ റിപ്പോ ക്ലോൺ ചെയ്യരുത്. നിങ്ങളുടെ നാൽക്കവലയിലേക്ക് പോയി അത് ക്ലോൺ ചെയ്യുക.
റിപ്പോ ക്ലോൺ ചെയ്യാൻ, "കോഡ്" ക്ലിക്ക് ചെയ്യുക, തുടർന്ന് താഴെയുള്ള സ്ട്രിംഗ് പകർത്തുക.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-clone-1.png" alt="copy string" />
നിങ്ങൾ ഇപ്പോൾ ഡൗൺലോഡ് ചെയ്ത ഗീത് ബാഷ് ആപ്ലിക്കേഷൻ തുറക്കുക. ഇത് വിൻഡോസ് മെഷീനിലാണെങ്കിൽ താഴെയുള്ള ചിത്രം പോലെയായിരിക്കണം.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-1.png" alt="open git bash terminal" />
ഈ കമാൻഡ് ഉപയോഗിച്ച് ഈ പ്രോജക്റ്റ് സംരക്ഷിക്കാൻ നിങ്ങൾ ആഗ്രഹിക്കുന്ന ഫോൾഡറിലേക്ക് പോകുക
`cd <folder>`
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-2.png" alt="cd into a folder" />
ഈ കമാൻഡ് ഉപയോഗിച്ച് റിപ്പോസിറ്ററി ക്ലോൺ ചെയ്യുന്നതിന് മുകളിലുള്ള ഘട്ടത്തിൽ നിങ്ങൾ പകർത്തിയ സ്ട്രിംഗ് ഉപയോഗിക്കുക
`git clone <repo-url>`
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-clone-2.png" alt="clone the repository" />
നിങ്ങളുടെ മാറ്റങ്ങൾ വരുത്താൻ റിപ്പോ ഉള്ള ഡയറക്ടറിയിലേക്ക് പോയി അത് vs കോഡിൽ തുറക്കുക.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-3.png" alt="cd into the newly cloned repo" />
## Create a branch
ഇപ്പോൾ ഈ ലളിതമായ കമാൻഡ് ഉപയോഗിച്ച് ഒരു ബ്രാഞ്ച് സൃഷ്ടിക്കുക. ഈ കമാൻഡ് നിങ്ങൾക്കായി ഒരു ശാഖ സൃഷ്ടിക്കുക മാത്രമല്ല, ആ ബ്രാഞ്ചിലേക്ക് മാറാനും നിങ്ങളെ അനുവദിക്കുന്നു.
```
git checkout -b <ശാഖ-നാമം>
```
നിങ്ങളുടെ ശാഖയ്ക്ക് പേര് നൽകുക `<നിങ്ങളുടെ പേര് ചേർക്കുക>`. ഉദാഹരണത്തിന്, "ആഡ്-ജെയിംസ്-സ്മിത്ത്"
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-branch.png" alt="create a branch" />
## ആവശ്യമായ മാറ്റങ്ങൾ വരുത്തുകയും ആ മാറ്റങ്ങൾ വരുത്തുകയും ചെയ്യുക
ഇപ്പോൾ ഒരു ടെക്സ്റ്റ് എഡിറ്ററിൽ `Contributors.md` ഫയൽ തുറക്കുക, പേജിൻ്റെ താഴേക്ക് സ്ക്രോൾ ചെയ്ത് അതിൽ നിങ്ങളുടെ പേര് ചേർക്കുക, തുടർന്ന് ഫയൽ സംരക്ഷിക്കുക.
ഉദാഹരണം: നിങ്ങളുടെ പേര് ജെയിംസ് സ്മിത്ത് എന്നാണെങ്കിൽ, അത് ഇതുപോലെ ആയിരിക്കണം.
\[James Smith](https://github.com/jamessmith)
ഈ കമാൻഡ് പ്രവർത്തിപ്പിക്കുന്നതിലൂടെ Contributors.md-ൽ മാറ്റങ്ങൾ ഉണ്ടെന്ന് നിങ്ങൾക്ക് കാണാൻ കഴിയും
`git status`
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-status.png" alt="check the status" />
ഇപ്പോൾ ആ മാറ്റങ്ങൾ വരുത്തുക:
ആദ്യം ഉപയോഗിച്ച് സ്റ്റേജിംഗ് ഏരിയയിൽ നിങ്ങൾ വരുത്തിയ മാറ്റം ചേർക്കുക
`git add ഫയലിൻ്റെ പേര്`
തുടർന്ന് ഈ കമാൻഡ് പാടി ഒരു കമ്മിറ്റ് സന്ദേശം എഴുതുക
`git commit -m "സംഭാവകരുടെ പട്ടികയിൽ നിങ്ങളുടെ പേര് ചേർക്കുക"`
നിങ്ങളുടെ പേര് ഉപയോഗിച്ച് `<your-name>` മാറ്റിസ്ഥാപിക്കുക.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-commit.png" alt="commit changes" />
നിങ്ങളുടെ പ്രതിബദ്ധത പൂർത്തീകരിച്ചിട്ടുണ്ടോ എന്നറിയാൻ നിങ്ങൾക്ക് ഒരു ലളിതമായ `git log --oneline` കമാൻഡ് പ്രവർത്തിപ്പിക്കാം.
## മാറ്റങ്ങൾ Github-ലേക്ക് പുഷ് ചെയ്യുക
മുകളിലുള്ള ഘട്ടങ്ങൾ പൂർത്തിയാക്കിക്കഴിഞ്ഞാൽ, ഈ കമാൻഡ് ഉപയോഗിച്ച് നിങ്ങൾക്ക് മാറ്റങ്ങൾ വരുത്താൻ കഴിയും
`git push origin <branch-name>`
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-push.png" alt="push changes" />
## നിങ്ങളുടെ മാറ്റങ്ങൾ അവലോകനത്തിനായി സമർപ്പിക്കുക
നിങ്ങൾ github-ൽ നിങ്ങളുടെ ശേഖരണത്തിലേക്ക് പോയാൽ, നിങ്ങൾ `Compare & pull request` ബട്ടൺ കാണും. ആ ബട്ടണിൽ ക്ലിക്ക് ചെയ്യുക.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
ഇപ്പോൾ പുൾ റിക്വസ്റ്റ് സമർപ്പിക്കുക.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="submit pull request" />
ഉടൻ തന്നെ നിങ്ങളുടെ എല്ലാ മാറ്റങ്ങളും ഈ പ്രോജക്റ്റിൻ്റെ മാസ്റ്റർ ബ്രാഞ്ചിലേക്ക് ഞാൻ ലയിപ്പിക്കും. മാറ്റങ്ങൾ ലയിച്ചുകഴിഞ്ഞാൽ നിങ്ങൾക്ക് ഒരു അറിയിപ്പ് ഇമെയിൽ ലഭിക്കും.
## ഇവിടെ നിന്ന് എവിടെ പോകണം?
അഭിനന്ദനങ്ങൾ! നിങ്ങൾ ഒരു സംഭാവകൻ എന്ന നിലയിൽ പലപ്പോഴും കണ്ടുമുട്ടുന്ന സ്റ്റാൻഡേർഡ് _ഫോർക്ക് -> ക്ലോൺ -> എഡിറ്റ് -> PR_ വർക്ക്ഫ്ലോ പൂർത്തിയാക്കി!
[വെബ് ആപ്പ്](https://firstcontributions.github.io#social-share) എന്നതിലേക്ക് പോയി നിങ്ങളുടെ സംഭാവനകൾ ആഘോഷിക്കുകയും സുഹൃത്തുക്കളുമായും പിന്തുടരുന്നവരുമായും അത് പങ്കിടുകയും ചെയ്യുക.
നിങ്ങൾക്ക് എന്തെങ്കിലും സഹായം ആവശ്യമുണ്ടെങ്കിൽ അല്ലെങ്കിൽ എന്തെങ്കിലും ചോദ്യങ്ങൾ ഉണ്ടെങ്കിൽ ഞങ്ങളുടെ സ്ലാക്ക് ടീമിൽ ചേരാം. [സ്ലാക്ക് ടീമിൽ ചേരുക](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [അധിക മെറ്റീരിയൽ](../additional-material/git_workflow_scenarios/additional-material.md)
## മറ്റ് ടൂളുകൾ ഉപയോഗിച്ചുള്ള ട്യൂട്ടോറിയലുകൾ
[പ്രധാന താളിലേക്ക് മടങ്ങുക](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)