mirror of
https://github.com/LucasVbr/first-contributions.git
synced 2026-05-13 17:21:50 +00:00
Merge branch 'main' into fix/remove-slack-link-in-albanian-readme
This commit is contained in:
Roshan Jossy
@@ -31,7 +31,7 @@ If you're making changes to a translation, please request a review from our prev
|
||||
| ქართული | [Georgian](../translations/README.ka.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/9116447?s=460&v=4" alt="@iko1133" />](https://github.com/iko1133) |
|
||||
| Galego | [Galician](../translations/README.gl.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/16878891?s=460&v=4" alt="@siderio2" />](https://github.com/siderio2) |
|
||||
| Greek | [Greek](../translations/README.gr.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/63111742?v=4" alt="@adreaskar" />](https://github.com/adreaskar) [<img width="100" src="https://avatars.githubusercontent.com/u/19299306?v=4" alt="@porfanid" />](https://github.com/porfanid) |
|
||||
| Gujarati | [Gujarati](../translations/README.guj.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/38134283?s=460&v=4" alt="@smitgajjar" />](https://github.com/smitgajjar) [<img width="100" src="https://avatars.githubusercontent.com/u/16669911?v=4" alt="@kaushalgosaliya5" />](https://github.com/kaushalgosaliya5/) |
|
||||
| ગુજરાતી | [Gujarati](../translations/README.guj.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/38134283?s=460&v=4" alt="@smitgajjar" />](https://github.com/smitgajjar) [<img width="100" src="https://avatars.githubusercontent.com/u/16669911?v=4" alt="@kaushalgosaliya5" />](https://github.com/kaushalgosaliya5/) |
|
||||
| Hausa | [Hausa](../translations/README.hau.md) | []() |
|
||||
| עברית | [Hebrew](../translations/README.hb.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/23402988?s=460&v=4" alt="@TomerPacific" />](https://github.com/TomerPacific) |
|
||||
| हिन्दी | [Hindi](../translations/README.hi.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/4654382?s=460&v=4" alt="@arshadkazmi42" />](https://github.com/arshadkazmi42) [<img width="100" src="https://avatars2.githubusercontent.com/u/7047079?s=460&v=4" alt="@sara-02" />](https://github.com/sara-02) [<img width="100" src="https://avatars.githubusercontent.com/u/20799404?v=4" alt="shrut1996" />](https://github.com/shrut1996) |
|
||||
|
||||
+1085
-3476
File diff suppressed because it is too large
Load Diff
@@ -15,7 +15,7 @@
|
||||
<kbd>[<img title="Czech" alt="Czech" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/cz.svg" width="22">](docs/translations/README.cs.md)</kbd>
|
||||
<kbd>[<img title="Deutsch" alt="Deutsch" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/de.svg" width="22">](docs/translations/README.de.md)</kbd>
|
||||
<kbd>[<img title="Dansk" alt="Dansk" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/dk.svg" width="22">](docs/translations/README.da.md)</kbd>
|
||||
<kbd>[<img title="العربية" alt="العربية" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/eg.svg" width="22">](docs/translations/README.eg.md)</kbd>
|
||||
<kbd>[<img title="المصرية" alt="المصرية" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/eg.svg" width="22">](docs/translations/README.eg.md)</kbd>
|
||||
<kbd>[<img title="Dezéiriya" alt="Dezéiriya" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/dz.svg" width="22">](docs/translations/README.dz.md)</kbd>
|
||||
<kbd>[<img title="Español de España" alt="Español de España" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/es.svg" width="22">](docs/translations/README.es.md)</kbd>
|
||||
<kbd>[<img title="Française" alt="Française" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/fr.svg" width="22">](docs/translations/README.fr.md)</kbd>
|
||||
@@ -50,7 +50,7 @@
|
||||
<kbd>[<img title="Polski" alt="Polski" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/pl.svg" width="22">](docs/translations/README.pl.md)</kbd>
|
||||
<kbd>[<img title="Português (Portugal)" alt="Português (Portugal)" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/pt.svg" width="22">](docs/translations/README.pt-pt.md)</kbd>
|
||||
<kbd>[<img title="Русский язык" alt="Русский язык" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/ru.svg" width="22">](docs/translations/README.ru.md)</kbd>
|
||||
<kbd>[<img title="عربى" alt="عربى" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/sa.svg" width="22">](docs/translations/README.ar.md)</kbd>
|
||||
<kbd>[<img title="العربية" alt="العربية" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/sa.svg" width="22">](docs/translations/README.ar.md)</kbd>
|
||||
<kbd>[<img title="Svenska" alt="Svenska" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/se.svg" width="22">](docs/translations/README.se.md)</kbd>
|
||||
<kbd>[<img title="Slovenčina" alt="Slovenčina" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/sk.svg" width="22">](docs/translations/README.slk.md)</kbd>
|
||||
<kbd>[<img title="Slovenščina" alt="Slovenščina" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/si.svg" width="22">](docs/translations/README.sl.md)</kbd>
|
||||
|
||||
@@ -1,73 +1,73 @@
|
||||
# .gitignore
|
||||
## Understanding .gitignore
|
||||
|
||||
The .gitignore file is a text file that tells Git which files or folders to ignore in a project.
|
||||
The `.gitignore` file is an essential component of Git's workflow. It tells Git which files and folders to ignore, preventing unnecessary or sensitive data from being tracked in your repository.
|
||||
|
||||
A local .gitignore file is usually placed in the root directory of a project. You can also create a global .gitignore file and any entries in that file will be ignored in all of your Git repositories.
|
||||
## Why Use .gitignore?
|
||||
|
||||
## Why .gitignore
|
||||
Now you may wonder why would you want git to ignore certain files and folders. Its because you don't want files like build files, cache files, other local configuration files like node modules, compilation files, temporary files IDE's create, etc to be tracked by git. It's usually used to avoid committing transient files from your working directory that aren't useful to other collaborators.
|
||||
Certain files should not be included in version control because they are either:
|
||||
- Temporary or system-generated (e.g., cache, build files, logs)
|
||||
- Large dependencies that can be reinstalled (e.g., `node_modules`)
|
||||
- Personal or sensitive configuration files (e.g., API keys, environment variables)
|
||||
- IDE or editor-specific files (e.g., `.vscode/`, `.idea/`)
|
||||
|
||||
## Getting started
|
||||
To create a local .gitignore file, create a text file and name it .gitignore (remember to include the . at the beginning). Then edit this file as needed. Each new line should list an additional file or folder that you want Git to ignore.
|
||||
Ignoring these files keeps the repository clean, reduces conflicts, and prevents security risks.
|
||||
|
||||
The entries in this file can also follow a matching pattern.
|
||||
## Creating a .gitignore File
|
||||
|
||||
```
|
||||
* is used as a wildcard match
|
||||
/ is used to ignore path names relative to the .gitignore file
|
||||
# is used to add comments to a .gitignore file
|
||||
To create a `.gitignore` file:
|
||||
1. In your project root directory, create a new text file named `.gitignore`.
|
||||
2. List the files and folders you want to ignore, one per line.
|
||||
3. Save the file.
|
||||
|
||||
This is an example of what the .gitignore file could look like:
|
||||
### Basic Syntax for .gitignore
|
||||
- `*` → Wildcard for matching multiple files.
|
||||
- `/` → Specifies path relative to `.gitignore`.
|
||||
- `#` → Adds comments.
|
||||
|
||||
### Example .gitignore File:
|
||||
```sh
|
||||
# Ignore Mac system files
|
||||
.DS_store
|
||||
.DS_Store
|
||||
|
||||
# Ignore node_modules folder
|
||||
node_modules
|
||||
# Ignore dependency folders
|
||||
node_modules/
|
||||
venv/
|
||||
|
||||
# Ignore log and cache files
|
||||
*.log
|
||||
.cache/
|
||||
|
||||
# Ignore environment files
|
||||
.env
|
||||
|
||||
# Ignore all text files
|
||||
*.txt
|
||||
|
||||
# Ignore files related to API keys
|
||||
.env
|
||||
|
||||
# Ignore SASS config files
|
||||
.sass-cache
|
||||
|
||||
```
|
||||
To add or change your global .gitignore file, run the following command:
|
||||
|
||||
```
|
||||
## Global .gitignore (For All Projects)
|
||||
To create a global `.gitignore` file (applies to all repositories):
|
||||
```sh
|
||||
git config --global core.excludesfile ~/.gitignore_global
|
||||
|
||||
```
|
||||
This will create the file ~/.gitignore_global. Now you can edit that file the same way as a local .gitignore file. All of your Git repositories will ignore the files and folders listed in the global .gitignore file.
|
||||
Then, edit `~/.gitignore_global` as you would a local `.gitignore`.
|
||||
|
||||
## How to Untrack Files Previously Committed from New Gitignore
|
||||
## Removing Files from Git Tracking
|
||||
|
||||
To untrack a single file, ie stop tracking the file but not delete it from the system use:
|
||||
If a file was already committed before adding it to `.gitignore`, you need to remove it from tracking:
|
||||
|
||||
- **Untrack a single file** (but keep it locally):
|
||||
```sh
|
||||
git rm --cached filename
|
||||
```
|
||||
|
||||
- **Untrack all ignored files**:
|
||||
```sh
|
||||
git rm -r --cached .
|
||||
git add .
|
||||
git commit -m "Updated .gitignore"
|
||||
```
|
||||
|
||||
To undo `git rm --cached filename`, use:
|
||||
```sh
|
||||
git add filename
|
||||
```
|
||||
git rm --cached filename
|
||||
```
|
||||
|
||||
To untrack every file in .gitignore:
|
||||
|
||||
First, commit any outstanding code changes, and then run:
|
||||
|
||||
```
|
||||
git rm -r --cached
|
||||
```
|
||||
|
||||
This removes any changed files from the index(staging area), then run:
|
||||
|
||||
```
|
||||
git add .
|
||||
```
|
||||
Commit it:
|
||||
|
||||
```
|
||||
git commit -m ".gitignore is now working"
|
||||
```
|
||||
|
||||
To undo ```git rm --cached filename```, use ```git add filename```
|
||||
|
||||
@@ -1,53 +1,75 @@
|
||||
# WHY USING BRANCHES DURING CONTRIBUTING
|
||||
## Why Use Branches When Contributing?
|
||||
Git branches are an essential tool for collaboration in software development. They allow multiple developers to work on different features or bug fixes simultaneously without interfering with the main project code. By using branches, you can experiment freely, test new ideas, and merge only the best changes into the main project.
|
||||
|
||||
## What are branches.
|
||||
## What Are Branches?
|
||||
A **branch** in Git is essentially a separate line of development. It allows you to create an isolated version of the project where you can make changes without affecting the main codebase. When you're ready, you can merge your branch back into the main project.
|
||||
|
||||
Branches are simply pointers to a commit.
|
||||
### How Branches Work
|
||||
Every branch is just a pointer to a specific commit in the project history. When you create a new branch, Git duplicates the state of the current branch, allowing you to work independently. New commits are added to this branch's history without affecting the main branch.
|
||||
|
||||
When you branch out, git is essentially making a new state of your current code, upon which you can work, without affecting the important main state of the code (which is in master branch).
|
||||
- To switch between branches, use `git checkout`.
|
||||
- To combine changes from one branch into another, use `git merge`.
|
||||
|
||||
When you are happy with your experiments, and want to merge you experiments in main code, you run git merge
|
||||
<branch name> master.
|
||||
This will tell git, to add in all changes from your experiment branch into master.
|
||||
## Why Use Branches?
|
||||
Branches make collaboration **structured and efficient**. Without them, all changes would be made directly to the main project, leading to confusion, errors, and conflicting code.
|
||||
|
||||
This way, while working in an open source project with a number of contributors, it becomes easy to merge the best suited code without altering the main code or master branch.
|
||||
### Example: The Car Paint Job Analogy
|
||||
Imagine a car manufacturing team deciding on the default color for a new car model. Initially, the car is set to be **olive green**. However, a few team members want to see how it looks in **red**.
|
||||
|
||||
## How it works?
|
||||
- Instead of repainting the original car, they create a **prototype** with red paint.
|
||||
- If the red color is approved, it replaces the original color (i.e., the branch is merged into the main project).
|
||||
- If the red color is rejected, the prototype is discarded (i.e., the branch is deleted).
|
||||
|
||||
A branch represents an independent line of development. Branches serve as an abstraction for the edit/stage/commit process. You can think of them as a way to request a brand new working directory, staging area, and project history. New commits are recorded in the history for the current branch, which results in a fork in the history of the project.
|
||||
Similarly, in Git, branches allow developers to test new features without directly modifying the main codebase.
|
||||
|
||||
The git branch command lets you create, list, rename, and delete branches. It doesn’t let you switch between branches or put a forked history back together again. For this reason, git branch is tightly integrated with the git checkout and git merge commands.
|
||||
## Feature Branching
|
||||
Instead of having one branch per developer, it's better to create **one branch per feature**. This keeps things organized and prevents unnecessary conflicts.
|
||||
|
||||
## Why to use branches?
|
||||
### Example: Alice & Bob's Feature Development
|
||||
- **Alice** is working on **Feature A** and makes several commits.
|
||||
- She then switches to **Feature C** and makes more commits.
|
||||
- Meanwhile, **Bob** finishes **Feature B** and wants to start working on **Feature A**.
|
||||
- Bob pulls in Alice’s branch, but now his branch contains **Feature A, Feature B, and some incomplete parts of Feature C**.
|
||||
- When he tries to merge his branch, he faces conflicts because Feature C is unfinished.
|
||||
|
||||
If the question "Why do we use branching in version control like git?" still persists in your mind, here's a quick explanation:
|
||||
To avoid this:
|
||||
- Alice should have separate branches for **Feature A** and **Feature C**.
|
||||
- Bob should have separate branches for **Feature B** and **Feature A**.
|
||||
|
||||
Let's take a simple example to understand the branching strategy. A production car needs a paint job before its launch. Prior to its official sale, it was decided that the car would come in 'olive green' color as default. But some of the members in the manufacturing team decided to showcase the car in 'red' color. Hence an ambiguous situation arises and to avoid this problem branching was introduced.The red color paint job is like a branch to the master repository 'Car'. Pushing this branch will suggest the red color. If merged with the master repository the car will get the red color otherwise it will continue with olive green. Merging a contributors branch to the master repo of the organization depends on the project head.
|
||||
This way, they can work without interfering with each other's progress.
|
||||
|
||||
## Example
|
||||
|
||||
Alice is working on Feature A and Bob is working on Feature B. Alice is halfway done with Feature A and has made a few commits in alice. However, Feature A is quite hard to implement so Alice decides that she should rather work on Feature C and makes a few commits onto alice. Bob finished Feature B and decides that he would like to tackle Feature A and so pulls alice into bob.
|
||||
|
||||
After Bob finishes Feature A he would like to merge bob into master. However, bob now contains Feature A, Feature B and parts of Feature C, but Feature C is not ready to be merged! It's easy to see that a workflow like this can lead to many confusing merge conflicts.
|
||||
|
||||
The trick is that instead of having personal branches one should have feature branches. Alice should have a branch for Feature A and Feature C and Bob should have a branch for Feature B and Feature A. That way they both can work on different features without tramping on each other's toes.
|
||||
|
||||
## How to create branches?
|
||||
|
||||
#### Create a branch
|
||||
## Creating and Managing Branches
|
||||
|
||||
### Create a New Branch
|
||||
```sh
|
||||
git branch my-new-branch
|
||||
```
|
||||
git branch AnyBranchName
|
||||
This creates a new branch named `my-new-branch` without switching to it.
|
||||
|
||||
### Switch to a Branch
|
||||
```sh
|
||||
git checkout my-new-branch
|
||||
```
|
||||
This moves you to `my-new-branch`, allowing you to work on it.
|
||||
|
||||
A new branch will be created named AnyBranchName and all the file changes in this branch will not be affected in the main branch.
|
||||
For detailed explanation refer [How to create branch](https://www.atlassian.com/git/tutorials/using-branches)
|
||||
|
||||
#### Delete the branch
|
||||
|
||||
```
|
||||
git branch -d AnyBranchName
|
||||
### Create and Switch to a Branch (Shortcut)
|
||||
```sh
|
||||
git checkout -b my-new-branch
|
||||
```
|
||||
This creates and switches to the new branch in a single step.
|
||||
|
||||
Branch name AnyBranchName will be deleted from the git repository.
|
||||
Refer to [Removing branch from your repository](https://github.com/jashnimje/first-contributions/blob/7dcae72208e4b42fcf834b4f189fa8ee78238077/additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md)
|
||||
### Delete a Branch (After Merging)
|
||||
```sh
|
||||
git branch -d my-new-branch
|
||||
```
|
||||
This removes `my-new-branch` if it has already been merged.
|
||||
|
||||
### Force Delete a Branch (Without Merging)
|
||||
```sh
|
||||
git branch -D my-new-branch
|
||||
```
|
||||
Use this with caution! It deletes the branch even if it has unmerged changes.
|
||||
|
||||
## Additional Resources
|
||||
- [Git Branching Guide (Atlassian)](https://www.atlassian.com/git/tutorials/using-branches)
|
||||
- [Removing a Branch from Your Repository](https://github.com/jashnimje/first-contributions/blob/7dcae72208e4b42fcf834b4f189fa8ee78238077/additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md)
|
||||
|
||||
@@ -114,8 +114,7 @@ Urime! Ti sapo ke kompletuar procesin _fork -> clone -> edit -> PR_ që do ta ha
|
||||
|
||||
Festoje kontributin tënd dhe ndaje me shokët dhe ndjekësit duke shkuar te [web aplikacioni](https://firstcontributions.github.io/#social-share).
|
||||
|
||||
Ti mund të kontribuosh në kodin tonë duke vizituar [repositorin e kontributeve](https://github.com/firstcontributions/first-contributions).
|
||||
|
||||
Nëse dëshiron më shumë praktikë, shiko [kontributet e kodit](https://github.com/roshanjossey/code-contributions)
|
||||
|
||||
Tani të të ndihmojmë që të kontribuosh në projekte tjera. Ne kemi krijuar një listë projektesh me probleme të lehta tek të cilat mund të fillosh. Shiko [listën e projekteve në web apliacion](https://firstcontributions.github.io/#project-list).
|
||||
|
||||
|
||||
@@ -121,7 +121,7 @@ git push origin -u <your-new-branch-name>
|
||||
|
||||
আপনার অবদানের আনন্দ উপভোগ করুন এবং [ওয়েব অ্যাপ](https://firstcontributions.github.io/#social-share)-এর মাধ্যমে বন্ধু ও অনুসরণকারীদের সাথে শেয়ার করুন।
|
||||
|
||||
যদি আপনি আরও অনুশীলন করতে চান, তাহলে [কোড অবদানগুলি](https://https://github.com/roshanjossey/code-contributions) চেকআউট করুন।
|
||||
যদি আপনি আরও অনুশীলন করতে চান, তাহলে [কোড অবদানগুলি](https://github.com/roshanjossey/code-contributions) চেকআউট করুন।
|
||||
|
||||
এখন আপনি অন্যান্য প্রজেক্টগুলোতেও অবদান রাখতে পারেন। আপনার সুবিধার্থে আমরা সহজ সমস্যা সম্বলিত প্রজেক্টগুলোর একটি তালিকা তৈরি করেছি। ওয়েব অ্যাপে [প্রজেক্টগুলোর তালিকা](https://firstcontributions.github.io/#project-list) দেখুন।
|
||||
|
||||
|
||||
@@ -9,11 +9,11 @@
|
||||
Este proyecto tiene como objetivo simplificar y guiar la forma en que los principiantes hacen su primera contribución. Si está buscando hacer su primera contribución, siga los pasos a continuación.
|
||||
|
||||
|
||||
#### *Si eres un neófit@ con la linea de comandos, [](#Tutoriales-usando-otras-herramientas)*
|
||||
#### *Si no estás familiarizado con la línea de comandos, [aquí hay tutoriales usando herramientas con Interfaz Gráfica (GUI)](#tutoriales-usando-otras-herramientas)*
|
||||
|
||||
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork de este repositorio" />
|
||||
|
||||
En caso de no tener instalado Git en tu equipo, te dejo una para [guia]( https://git-scm.com/book/es/v2/Inicio---Sobre-el-Control-de-Versiones-Instalaci%C3%B3n-de-Git) para instalarlo.
|
||||
En caso de no tener instalado Git en tu equipo, te dejo una [guia]( https://git-scm.com/book/es/v2/Inicio---Sobre-el-Control-de-Versiones-Instalaci%C3%B3n-de-Git) para instalarlo.
|
||||
|
||||
## Has un "Fork" de este repositorio
|
||||
|
||||
@@ -23,15 +23,15 @@ Presiona el boton "fork" de este repositorio en la parte superior derecha de la
|
||||
|
||||
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clonar este repositorio" />
|
||||
|
||||
Ahora clona el repositorio al que le hiciste un fork previamente, el URL del repositorio deberia estar asi `https://github.com/<tu-usuario>/first-contributions`. Entra en tu cuenta de Github, y has click en el botón `clone or download` y luego has clic en el ícono para `copy`.
|
||||
Ahora clona el repositorio al que le hiciste un fork previamente, el URL del repositorio deberia estar asi `https://github.com/<tu-usuario>/first-contributions`. Entra en tu cuenta de Github, y has click en el botón `Code` y luego en la pestaña SSH y luego haz clic en el icono de _copiar al portapapeles_.
|
||||
|
||||
Abre tu terminal y ejecuta el siguiente comando:
|
||||
Abre tu terminal y ejecuta el siguiente comando git:
|
||||
|
||||
```
|
||||
git clone "la url del repositorio que copiaste"
|
||||
```
|
||||
|
||||
Donde "la url del repositorio que copiaste" (sin las comillas dobles) es la *url* a este repositorio se veria algo asi `https://github.com/<tu-usuario>/first-contributions.git`(tu *fork* a este proyecto).
|
||||
Donde "la url del repositorio que copiaste" (sin las comillas dobles) es la *url* a este repositorio (tu *fork* a este proyecto), se veria algo asi `https://github.com/<tu-usuario>/first-contributions.git` .
|
||||
|
||||
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="copiar URL al portapapeles" />
|
||||
|
||||
@@ -39,7 +39,7 @@ Por ejemplo:
|
||||
```
|
||||
git clone https://github.com/<tu-usuario>/first-contributions.git
|
||||
```
|
||||
Donde `<tu-usuario>` es tu usuario de GitHub. Con este comando estas copiando loslos contenidos del repositorio *first-contributions* de GitHub a tu equipo.
|
||||
Donde `<tu-usuario>` es tu nombre de usuario de GitHub. Con este comando estas copiando los contenidos del repositorio *first-contributions* de GitHub a tu equipo.
|
||||
|
||||
## Crea una rama (*Branch*)
|
||||
|
||||
@@ -49,19 +49,28 @@ Cambia al directorio del repositorio en tu equipo (si es que no estás ahí ya).
|
||||
cd first-contributions
|
||||
```
|
||||
|
||||
Ahora crea una rama (*branch*) usando el comando `git checkout`:
|
||||
Ahora crea una rama (*branch*) usando el comando `git checkout` o `git switch`:
|
||||
```
|
||||
git checkout -b <dale un nombre>
|
||||
git switch -c <dale un nombre>
|
||||
```
|
||||
|
||||
Por ejemplo:
|
||||
```
|
||||
git checkout -b add-julio-jaramillo
|
||||
git switch -c add-julio-jaramillo
|
||||
```
|
||||
<details>
|
||||
<summary> <strong>Si obtienes algún error usando git switch, haz clic aquí:</strong> </summary>
|
||||
|
||||
Si aparece el mensaje de error "Git: `switch` no es un comando git. Consulta `git –help`", es probable que estés usando una versión anterior de git.
|
||||
|
||||
En este caso, intenta usar git checkout en su lugar.
|
||||
</details>
|
||||
|
||||
## Haz los cambios necesarios y has un "Commit" de esos cambios
|
||||
|
||||
Abre el archivo `Contributors.md` en un editor de texto y añade tu nombre. No lo añadas ni al principio ni al final del archivo, hazlo en cualquier otro sitio. Guarda el archivo.
|
||||
Abre el archivo `Contributors.md` en un editor de texto y añade tu nombre. No lo añadas ni al principio ni al final del archivo, hazlo en cualquier otro sitio. Ahora guarda el archivo.
|
||||
|
||||
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
|
||||
|
||||
@@ -82,12 +91,35 @@ reemplazando `<nombre>` con tu nombre.
|
||||
|
||||
## Haz un "Push" de tus cambios a GitHub
|
||||
|
||||
Mandar un *push* de tus cambios usando el comando `git push`:
|
||||
Envía tus cambios usando el comando `git push`:
|
||||
```
|
||||
git push origin <nombre-rama>
|
||||
git push -u origin <nombre-rama>
|
||||
```
|
||||
Reemplaza `<nombre-rama>` con el nombre de la rama que creaste anteriormente.
|
||||
|
||||
<details>
|
||||
<summary> <strong>Si obtienes algún error al enviar (Push), haz clic aquí:</strong> </summary>
|
||||
|
||||
- ### Error de Autenticación
|
||||
<pre>remote: El soporte para la autenticación de contraseña se eliminó el 13 de agosto de 2021. Utiliza un token de acceso personal en su lugar.
|
||||
remote: Consulta [https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/](https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/) para obtener más información.
|
||||
fatal: Fallo en la autenticación para '[https://github.com/](https://github.com/)<tu-usuario>/first-contributions.git/'</pre>
|
||||
Ve al [tutorial de GitHub](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) sobre cómo generar y configurar una clave SSH en tu cuenta.
|
||||
|
||||
Además, es posible que desees ejecutar `git remote -v` para verificar tu dirección remota.
|
||||
|
||||
Si se ve algo como esto:
|
||||
<pre>origin [https://github.com/tu-usuario/tu_repo.git] (fetch)
|
||||
origin [https://github.com/tu-usuario/tu_repo.git] (push)</pre>
|
||||
|
||||
|
||||
cámbialo usando este comando:
|
||||
```bash
|
||||
git remote set-url origin git@github.com:tu-usuario/tu_repo.git
|
||||
```
|
||||
De lo contrario, aún se te pedirá un nombre de usuario y contraseña y obtendrás un error de autenticación.
|
||||
</details>
|
||||
|
||||
## Envía (*Submit*) tus cambios para ser revisados
|
||||
|
||||
Si vas a tu repositorio en GitHub, verás un botón `Compare & pull request`. Haz clic sobre este botón.
|
||||
@@ -104,9 +136,9 @@ Pronto estaré combinando tus cambios (haciendo *merge*) con la rama master de e
|
||||
|
||||
¡Felicidades! ¡Has completado la línea de trabajo *_fork -> clone -> edit -> PR_* que encontrarás habitualmente como contribuidor!
|
||||
|
||||
Festeja tu contribución y compártela con tus amigos y seguidores yendo a [web app](https://firstcontributions.github.io/#social-share).
|
||||
Festeja tu contribución y compártela con tus amigos y seguidores yendo a la [web app](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 Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
|
||||
Si deseas más práctica, consulta [code contributions](https://github.com/roshanjossey/code-contributions).
|
||||
|
||||
Ahora empieza a contribuir a otros proyectos. Hemos reunido una lista de proyectos con *issues* sencillas para que puedas empezar. Échale un ojo a la [lista de proyectos en la web app](https://firstcontributions.github.io/#project-list).
|
||||
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
[](https://github.com/ellerbrock/open-source-badges/)
|
||||
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
[](https://www.codetriage.com/roshanjossey/first-contributions)
|
||||
# <div dir="rtl">مساهمتك الأولى</div>
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
[](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)
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
[](https://www.codetriage.com/roshanjossey/first-contributions)
|
||||
|
||||
@@ -117,8 +116,6 @@ Well done! Ye jus' completed th' standard _fork -> clone -> edit -> PR_ workflow
|
||||
|
||||
Celebrate yer contribution 'n share it wit' yer hearties 'n followers by goin' t' [web app](https://firstcontributions.github.io/#social-share).
|
||||
|
||||
Ye could join our slack crew in case ye needs any help or 'ave any riddles. [Join our slack crew](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
|
||||
|
||||
Now let's get ye started wit' contributin' t' other projects. We've compiled a list o' projects wit' easy issues ye can get started on. Check out [th' list o' projects in web app](https://firstcontributions.github.io/#project-list).
|
||||
|
||||
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
|
||||
|
||||
@@ -49,7 +49,7 @@ git clone https://github.com/this-is-you/first-contributions.git
|
||||
cd first-contributions
|
||||
```
|
||||
|
||||
Τώρα δημιουργείστε ένα νέο παρακλάδι χρησιμοποιώντας την εντολή `git switch` :
|
||||
Τώρα δημιουργήστε ένα νέο παρακλάδι χρησιμοποιώντας την εντολή `git switch` :
|
||||
|
||||
```
|
||||
git switch -c your-new-branch-name
|
||||
@@ -63,7 +63,7 @@ git switch -c add-alonzo-church
|
||||
|
||||
(Το όνομα του παρακλαδιού δεν χρειάζεται να περιέχει την λέξη _add_ αλλά είναι λογικό να την συμπεριλάβουμε μιας και ο σκοπός του παρακλαδιού είναι να προσθέσουμε το όνομα μας σε μια λίστα.)
|
||||
|
||||
## Πραγματοποιήστε τις αλλαγές και αποθηκεύστετες (add & commit)
|
||||
## Πραγματοποιήστε τις αλλαγές και αποθηκεύστε τες (add & commit)
|
||||
|
||||
Τώρα ανοίξτε το αρχείο `Contributors.md` με έναν επεξεργαστή κειμένου. Χρειάζεται να είστε εξοικειωμένοι με την Markdown, μια ελαφριά γλώσσα σήμανσης. Δείτε στο [cheat sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) για το πως να χρησιμοποιήσετε την Markdown.
|
||||
|
||||
@@ -107,13 +107,13 @@ git push origin <add-your-name>
|
||||
|
||||
όπου `<add-your-name>` αντικαταστήστε με το όνομα του παρακλαδιού(branch) που δημιουργήσατε προηγουμένως
|
||||
|
||||
## Υποβάλλετε τις αλλαγές σας για έλεγχο
|
||||
## Υποβάλετε τις αλλαγές σας για έλεγχο
|
||||
|
||||
Εάν πάτε στο αποθετήριο (repository) στο github θα δείτε ένα κουμπί με τίτλο `Compare & pull request`. Κάντε κλικ σε αυτό το κουμπί.
|
||||
|
||||
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
|
||||
|
||||
Τώρα υποβάλλετε το pull request.
|
||||
Τώρα υποβάλετε το pull request.
|
||||
|
||||
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
|
||||
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
[](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)
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
[](https://www.codetriage.com/roshanjossey/first-contributions)
|
||||
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
[](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)
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
|
||||
# ਪਹਿਲਾ ਯੋਗਦਾਨ
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
[](https://github.com/firstcontributions/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)
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
[](https://www.codetriage.com/roshanjossey/first-contributions)
|
||||
|
||||
@@ -78,7 +77,7 @@ git checkout -b உங்கள்-கிளையின்-பெயர்
|
||||
|
||||
## தேவையான மாற்றங்களைச் செய்து அந்த மாற்றங்களை commit செய்யுங்கள்
|
||||
|
||||
இப்போது *text editor* அல்லது *notepad* இல் `Contribitors.md` கோப்பைத் திறந்து, அதில் உங்கள் பெயரைச் சேர்க்கவும். கோப்பின் தொடக்கத்திலோ அல்லது முடிவிலோ இதைச் சேர்க்க வேண்டாம். இடையில் எங்கும் வைக்கவும். இப்போது, கோப்பை சேமிக்கவும்.
|
||||
இப்போது *text editor* அல்லது *notepad* இல் `Contributors.md` கோப்பைத் திறந்து, அதில் உங்கள் பெயரைச் சேர்க்கவும். கோப்பின் தொடக்கத்திலோ அல்லது முடிவிலோ இதைச் சேர்க்க வேண்டாம். இடையில் எங்கும் வைக்கவும். இப்போது, கோப்பை சேமிக்கவும்.
|
||||
|
||||
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
|
||||
|
||||
@@ -141,7 +140,7 @@ GitHub இல் உள்ள உங்கள் களஞ்சியத்த
|
||||
|
||||
உங்கள் பங்களிப்பைக் கொண்டாடுங்கள் மற்றும் உங்கள் நண்பர்கள் மற்றும் பின்தொடர்பவர்களுடன் [web app](https://firstcontributions.github.io/#social-share) சென்று பகிர்ந்து கொள்ளுங்கள்.
|
||||
|
||||
உங்களுக்கு ஏதேனும் உதவி தேவைப்பட்டால் அல்லது ஏதேனும் கேள்விகள் இருந்தால் எங்கள் slack team இல் இணையலாம். [Join our slack crew](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)..
|
||||
உங்களுக்கு மேலும் பயிற்சி தேவைப்பட்டால், [code contributions](https://github.com/roshanjossey/code-contributions) என்னும் செயலை சரிபார்க்கலாம்.
|
||||
|
||||
இப்போது மற்ற திட்டங்களுக்கு பங்களிப்பதன் மூலம் தொடங்குவோம். நீங்கள் தொடங்கக்கூடிய எளிதான சிக்கல்களுடன் திட்டங்களின் பட்டியலை நாங்கள் தொகுத்துள்ளோம். பாருங்கள் [the list of projects in the web app](https://firstcontributions.github.io/#project-list).
|
||||
|
||||
|
||||
@@ -127,6 +127,9 @@ Tabriklayman! Siz horizgina contributor sifatida tez-tez uchraydigan standard is
|
||||
|
||||
Hissangizni nishonlang va [web app](https://firstcontributions.github.io/#social-share)ga o'tish orqali do'stlaringizga va ergashuvchilaringizga ulashing.
|
||||
|
||||
Agar ko‘proq mashq qilishni xohlasangiz, [code contributions](https://github.com/firstcontributions/first-contributions/blob/main/code-contributions.md) faylini ko‘rib chiqing.
|
||||
|
||||
|
||||
|
||||
Agar koʻproq mashq qilishni istasangiz, [kod hissalarini](https://github.com/roshanjossey/code-contributions) tekshiring.
|
||||
|
||||
|
||||
@@ -86,7 +86,7 @@ git push origin <add-your-name>
|
||||
將 `<add-your-name>` 替換為之前新建的分支名稱。
|
||||
|
||||
<details>
|
||||
<summary> <strong>如果在 push（發佈）过程中出 error（錯誤），點擊這裡</strong> </summary>
|
||||
<summary> <strong>如果在 push（發佈）過程中出 error（錯誤），點擊這裡</strong> </summary>
|
||||
|
||||
- ### Authentication Error
|
||||
<pre>remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
|
||||
|
||||
Reference in New Issue
Block a user