Add Tamara S to Contributors list

Created by: tmrpc

.github/CONTRIBUTING.md

+# Contribution guide
+
+Welcome to your first contribution. :heart:
+
+#### Before Contributing:
+You need to run it locally on your desktop.
+
+In order to do that, move to the desired location where package.json file is located
+
+- Install npm(latest version) -
+    npm is distributed with Node.js - which means that when you download Node.js,
+    you automatically get npm installed on your computer.
+    https://www.npmjs.com/get-npm
+- Install all the dependencies used by this project.
+   Use this command:  `install npm`
+
+- Run these final commands to run it locally:
+
+  `npm run build`
+  
+  `npm start`
+
+### Table Of Contents
+- [Code of Conduct](#code-of-conduct)
+- [Translation Guide](#translation-guide)
+
+## Code of Conduct
+If you want to contribute, you need to know a few things.
+
+[Code of conduct](../CODE_OF_CONDUCT.md)
+
+## Translation Guide
+We have some rules for translation. If you make the first translation for your language, you must add your language list on `Translations.md`.
+
+### Example
+
+`Translations.md`
+```markdown
+|Country | Translated Link |
+| --- | --- |
+| English | [English](../README.md) |
+| 🇮🇳 India | [Hindi](../translations/README.hi.md) |
+| 🇲🇲 Myanmar | [Myanmar Unicode](../translations/README.mm_unicode.md), Myanmar ZawGyi |
+```
+
+## TODO
+- [ ] Fix the grammar for the contribution guide.
+- [ ] Add more examples and more guides.
+
+
+Thanks! :heart:

.github/ISSUE_TEMPLATE.md

+<!--- Provide a general summary of the issue in the Title above -->
+
+🐞 **Problem**
+<!--- Provide a detailed description of the change or addition you are proposing -->
+<!--- If it is a feature or a bug, what problem is it solving-->
+
+🎯 **Goal**
+<!--- Why is this change important to you? How would you use it? -->
+<!--- How can it benefit other users? -->
+
+💡 **Possible solutions**
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->
+
+📋  **Steps to solve the problem**
+
+*   Comment below about what you've started working on.
+*   Add, commit, push your changes.
+*   Submit a pull request and add this in comments - `Addresses #<put issue number here>`
+*   Ask for a review in comments section of pull request.
+*   Celebrate your contribution to this project. 🎉

additional-material/git_workflow_scenarios/Useful-links-for-further-learning.md

+# Useful Links
+
+This document is dedicated to all the blog posts, helpful sites, tips and tricks websites that makes our lives easier. That we refer to for all our needs, be it a beginner or an expert. This page should act as an index of all those useful links that would help everybody who is new in the open-source domain or someone who wants to learn more.
+
+## The List
+1.  [Interactive tutorial to git](https://try.github.io)
+2.  [git - the simple guide](http://rogerdudler.github.io/git-guide/)
+3.  [On undoing, fixing, or removing commits in git](http://sethrobertson.github.io/GitFixUm/fixup.html)
+4.  [Git and GitHub tutorial translated to many languages](https://github.com/Roshanjossey/first-contributions)
+5.  [Merge Conflicts](https://www.git-tower.com/learn/git/ebook/en/command-line/advanced-topics/merge-conflicts)
+6.  [Resolving Merge Conflicts](https://githowto.com/resolving_conflicts)
+7. [Basics of Git - The Simple Quick Start Guide](https://blog.praveen.science/basics-of-git-the-quick-start-guide/)
+8. [Git Standards followed in our way of Spotify Agile Methodology](https://blog.praveen.science/git-standards-followed-in-our-way-of-spotify-agile-methodolgy/)
+9. [Git Shortcuts](https://blog.praveen.science/git-shortcuts/)
+10.  [Official Git cheat sheet in many languages](https://services.github.com/on-demand/resources/cheatsheets)
+11.  [Git cheat sheet from Tower](https://www.git-tower.com/learn/cheat-sheets/git)
+12.  [Common Git Problems](https://www.codementor.io/citizen428/git-tutorial-10-common-git-problems-and-how-to-fix-them-aajv0katd)
+13. [Git Rebase](https://blog.gitprime.com/git-rebase-an-illustrated-guide/)
+14. [Beginner's Guide to Rebasing and Squashing](https://github.com/servo/servo/wiki/Beginner%27s-guide-to-rebasing-and-squashing)
+15. [Git Cheatsheet that shows correlations between commands and files](http://ndpsoftware.com/git-cheatsheet.html)
+16. [How to contribute](https://opensource.guide/how-to-contribute/)
+17. [Getting started with Open Source](https://github.com/OpenSourceHelpCommunity/Getting-Started-With-Contributing-to-Open-Sources)
+18. [How to contribute](https://github.com/freeCodeCamp/how-to-contribute-to-open-source)
+19. [Atlassians Git Tutorials](https://www.atlassian.com/git)
+20. [Pull request reviews](https://help.github.com/articles/about-pull-request-reviews/)
+21. [Another Interactive tutorial for git](https://learngitbranching.js.org/)
+22. [Git commandline cheat-sheet](https://gist.github.com/davfre/8313299)
+23. [Programming Books](https://github.com/EbookFoundation/free-programming-books)
+24. [E-Book of professional tip and secrets](https://goalkicker.com/GitBook/GitProfessionalTipsSecrets.pdf)
+25. [tutorial about simple rules of become git professional](https://medium.freecodecamp.org/follow-these-simple-rules-and-youll-become-a-git-and-github-master-e1045057468f)
+
+Keep adding more links, that you find helpful.

additional-material/git_workflow_scenarios/additional-material.md

+# Additional information
+
+We assume that you have already finished with the basic tutorial before coming here. The additional information will give you some information about advanced Git techniques.
+
+### [Amending a commit](amending-a-commit.md)
+This document provides information about how to amend a commit on the remote repository.
+> Use this when you need to adjust a commit you made.
+
+### [Configuring git](configuring-git.md)
+This document provides information about how to configure user details and other options in git.
+> Use this to better control your git configurations.
+
+### [Keeping your fork synced with the repository](keeping-your-fork-synced-with-this-repository.md)
+This document provides information about how to keep your forked repository up-to-date with the base repository. This is important, as hopefully you and many others will contribute to the project.
+> Follow these steps if your fork doesn't have any changes in parent repository.
+
+### [Moving a Commit to a different Branch](moving-a-commit-to-a-different-branch.md)
+This document provides information about how to move a Commit to another Branch.
+> Take these steps to move a commit to another branch.
+
+### [Removing a File](removing-a-file.md)
+This document provides information about how to remove a file from your local repository.
+> Follow these steps to learn how to remove a file prior to a commit
+
+### [Removing a branch from your repository](removing-branch-from-your-repository.md)
+This document provides information about how to delete a branch from your repository.
+> Only do these steps after your pull request get's merged.
+
+### [Resolving Merge Conflicts](resolving-merge-conflicts.md)
+This document provides information about how to resolve merge conflicts.
+> Take these steps to resolve the annoying merge conflicts.
+
+### [Reverting a commit](reverting-a-commit.md)
+This document provides information about how to revert a commit on the remote repository. It comes in handy in case for when you need to undo a commit that has already been pushed to Github.
+> Take these steps if you want to reverse a commit.
+
+### [Squashing Commits](squashing-commits.md)
+This document provides information about how to squash commits with an interactive rebase.
+> Use this if you want to open a PR in an open source project and the reviewer asks you to squash every commit into one, with an informative commit message.
+
+### [Undo-ing a local commit](undoing-a-commit.md)
+This document provides information about how to undo a commit on your local repository. This is what you need to do when you feel you've messed up your local repository and wish to reset the local repository.
+> Take these steps if you want to undo/reset a local commit.
+
+### [Useful Links](Useful-links-for-further-learning.md)
+This document is dedicated to all the blog posts, helpful sites, tips and tricks websites that makes our lives easier. That we refer to for all our needs, be it a beginner or an expert. This page should act as an index of all those useful links that would help everybody who is new in the open-source domain or someone who wants to learn more.

additional-material/git_workflow_scenarios/amending-a-commit.md

+# Amending a Commit
+
+What if you commit a change to your remote repository only to realize later that you have a typo in the commit message or you forgot to add a line in your most recent commit.
+How do you edit that? This is what this tutorial covers.
+
+## Changing a recent commit message after you have pushed to Github.
+To do this without opening a file:
+*   Type in the ```git commit --amend -m "followed by your new commit message"```
+*   Run ```git push origin <branch-name>``` to commit the changes to the repository.
+
+Note: If you type in just ```git commit --amend```, your text editor would open up prompting you to edit the commit message.
+Adding the ``-m`` flags prevents it.
+
+## Modifying on a single commit
+
+So, what if we forgot to make a minor change to a file like changing a single word and we have already pushed the commit to our remote repository?
+
+To illustrate here is a log of my commits:
+```
+g56123f create file bot file
+a2235d updated contributor.md
+a5da0d modified bot file
+```
+Let's say I forgot to add a single word to the bot file
+
+There are 2 ways to go about this. The first is to have an entirely new commit that contains the change like so:
+```
+g56123f create file botfile
+a2235d updated contributor.md
+a5da0d modified botfile
+b0ca8f added single word to botfile
+```
+The second way is to amend the a5da0d commit, add this new word and  push it to Github as one commit.
+The second sounds better since it is just a minor change.
+
+To achieve this, we would do the following:
+*   Modify the file. In this case, I will modify the botfile to include the word I omitted previously.
+*   Next, add the file to the staging area with ```git add <filename>```
+
+Usually after adding files to the staging area, the next thing we do is git commit -m "our commit message" right?
+But since what we want to achieve here is to amend the previous commit, we would instead run:
+
+* ```git commit --amend```
+ This would then bring up the text editor and prompt you to edit the message. You can decide to leave the message as it was before or change it.
+* Exit the editor
+* Push your changes with `` `git push origin <branch-name>` ``
+
+That way, both changes would be in one single commit.

additional-material/git_workflow_scenarios/configuring-git.md

+# Configuring git
+
+The first time you tried to commit using git, you might have gotten a prompt like the one below:
+
+```bash
+$ git commit
+*** Please tell me who you are.
+
+Run
+
+git config --global user.email "you@example.com"
+git config --global user.name "Your Name"
+
+to set your account's default identity.
+Omit --global to set the identity only in this repository.
+```
+
+Git needs to know who you are when you create a commit. When you are working collaboratively, you should be able to see who modified what parts of the project and when, and thus, git has been designed to create commits tied to a name and an email.
+
+There are multiple ways to provide the `git commit` command with your email and name, and we'll go through some of them below.
+
+### Global Config
+
+When you store something in the global config, it is accessible system wide in all the repositories you work on. This is the preferred way and works for most use cases.
+
+To store something in the global config, you use the `config` command as follows:
+
+`$ git config --global <variable name> <value>`
+
+In the case of user details, we run it as follows:
+
+```
+$ git config --global user.email "you@example.com"
+$ git config --global user.name "Your Name"
+```
+
+### Repository Config
+
+As the name says, these configurations are scoped to your current repository. If you want to commit to a particular repository, say, a work related project, with your company's email, then you could use this method.
+
+To store something in the repository config, you use the `config` command  by emitting the `--global` flag as follows:
+
+`$ git config <variable name> <value>`
+
+In the case of user details, we run it as follows:
+
+```
+$ git config user.email "you@alternate.com"
+$ git config user.name "Your Name"
+```
+
+### Command-line Config
+
+These type of configurations are scoped to the current command only. All git commands take `-c` arguments before the action verb to set temporary configuration data.
+
+To store something in the command line config, run your command as follows:
+
+`$ git -c <variable-1>=<value> -c <variable-2>=<value> <command>`
+
+In our example, we would run the commit command as follows:
+
+`git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Your commit message"`
+
+### Note on Precedence
+
+Among the three methods described here, the precedence order is `command-line > repository > global`. This means that, if a variable is configured in the command-line as well as globally, the command-line value would be used for the operation.
+
+## Beyond User Details
+
+We have dealt with only the user details till now while working with the config. However, there are several other configuration options available. Some of them are:
+
+1.  `core.editor` - to specify the name of the editor used for writing commit messages, etc.
+2.  `commit.template` - to specify a file on the system as the initial commit template.
+3.  `color.ui` - to specify a boolean value for using colors in git's output.
+
+We have abstracted some details for ease of understanding. For further reading, head over to [git-scm.com](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration).

additional-material/git_workflow_scenarios/keeping-your-fork-synced-with-this-repository.md

+# Keeping your fork synced with this repository
+
+First, the flow for a full sync should be understood, which is important. In this schema, there are 3 different repos: my public repo on Github `github.com/Roshanjossey/first-contributions/`, your fork of the repo on GitHub `github.com/Your-Name/first-contributions/` and your local machine's repo from which you are suppose to work. This kind of cooperation is typical for open source projects and called `Triangle Workflows`.
+
+<img style="float;" src="../../assets/triangle_workflow.png" alt="triangle workflow" />
+
+To keep your two repos up-to-date with my public repo, so first we have to  fetch and merge the public repo with your local machine's repo.
+Our second move will be to push your local repo to your GitHub fork. As you've seen earlier, it's only from your fork that you can ask for a "pull request". So your GitHub fork is the last repo to be updated.
+
+Now, let's see how to do it:
+
+First, you must be on your master branch. To know which branch you are on, check the first line of:
+```
+git status
+```
+if you are not already on master:
+```
+git checkout master
+```
+
+Then you should add my public repo to your git with `add upstream remote-url`:
+```
+git remote add upstream https://github.com/Roshanjossey/first-contributions
+```
+This is a way of telling git that another version of this project exists in the specified url and we're calling it `upstream`. Once your git has a name let's fetch the latest version of the public repository:
+```
+git fetch upstream
+```
+
+You've just fetched the latest version of my fork (`upstream` remote). Now, you need to merge the public repository into your master branch.
+```
+git rebase upstream/master
+```
+Here you're merging the public repository with your master branch. Your local machine's master branch is now up-to-date. Lastly, if you push your master branch to your fork, your GitHub fork will also have the changes:
+```
+git push origin master
+```
+Notice here you're pushing to the remote named `origin`.
+
+So by now or at this point, all your repositories are up-to-date. Well done! You should do this, everytime your GitHub repo tells you that you are a few commits behind.

additional-material/git_workflow_scenarios/moving-a-commit-to-a-different-branch.md

+# Moving a commit to a different branch
+What if you commit a change, and then realize that you committed to a different branch?
+How can you change that? This is what this tutorial covers.
+
+## Moving the latest commits to an existing branch
+To do this, type:
+
+```git reset HEAD~ --soft``` - Undoes the last commit, but leave the changes available.  
+```git stash``` - Records the state of the directory.  
+
+```git checkout name-of-the-correct-branch``` - Switches to another branch.
+```git stash pop``` - Removes latest stashed state.  
+```git add .``` - Or try adding individual files.  
+```git commit -m "your message here"``` - Saves and Commits the changes.  
+
+Now your changes are on the correct branch
+
+
+### Moving the latest commits to a new Branch
+To do this, type:  
+```git branch newbranch``` -  Creates a new Branch. Saving all the Commits.  
+```git reset --hard HEAD~#``` - Move master back by # commits. Remember, these commits will be gone from master  
+```git checkout newbranch``` - Goes to the branch you created. It will have all the commits.  
+
+Remember: Any changes not committed will be LOST.

additional-material/git_workflow_scenarios/removing-a-file.md

+# Removing a file from Git
+
+Sometimes, you may want to remove a file from Git but not delete it from your computer. You can achieve this by using the following command:
+
+``git rm <file> --cached``
+
+## So what happened?
+
+Git will no longer keep track of changes in the removed file. As far as Git knows, it's as if you had deleted the file. If you were to locate the file in your file system, you will notice that it's still there.
+
+Notice that in the example above, the flag `--cached` is used. If we didn't add this flag, Git will remove the file from not just the repo, but from your file system too.
+
+If you commit the change with `git commit -m "Remove file1.js"` and pushed it to the remote repository using `git push origin master`, the remote repository will remove the file.
+
+## Additional features
+
+-   If you want to remove more than one file, you can include them all in the same command:
+
+    `git rm file1.js file2.js file3.js --cached`
+
+-   You can use a wildcard (*) to remove similar files. For example, if you would like to remove all .txt files from your local repository:
+
+    `git rm *.txt --cached`

additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md

+# Remove a branch from your repository
+
+If you have followed the tutorial up-to-now, our `<add-your-name>` branch has finished its purpose, it is time to delete it from your local machine's repo. This isn't necessary, but the name of this branch shows its rather special purpose. Its life can be made correspondingly short.
+
+First, let's merge your `<add-your-name>` to your master, so to go to your master branch:
+```
+git checkout master
+```
+
+Merge `<add-your-name>` to master:
+```
+git merge <add-your-name> master
+```
+
+Remove `<add-your-name>` on your local machine's repo:
+```
+git branch -d <add-your-name>
+```
+
+You have now deleted your local machine's `<add-your-name>` branch and everything looks neat and tidy.
+Though, at this point, you should still have the `<add-your-name>` branch in your GitHub fork. However, before you delete this, remember that you have sent a "Pull request" to my repo from this remote branch. So unless I've already merged it, don't delete this branch.
+
+However, if I have merged your branch and you want to delete the remote branch, use:
+```
+git push origin --delete <add-your-name>
+```
+
+Now, you know how to tidy your branches.
+With time, many commits will be added to my public repo. And the master branches of your local machine and of your GitHub fork won't be up-to-date. So in order to keep your repositories synchronized with mine, follow the steps below.
+
+#### [Keeping your fork synced with the repository](keeping-your-fork-synced-with-this-repository.md)

additional-material/git_workflow_scenarios/resolving-merge-conflicts.md

+# What is a merge conflict?
+
+When you try to merge another branch into your current working branch, you are taking changes from another context and combining them with your current working files.
+If two people have changed the same lines in the same file, or if one person decided to delete it while the other person decided to modify it, Git cannot identify which is the correct version. Git will then mark the file as having a conflict - which you'll have to resolve before you can continue your work.
+
+# How to resolve a merge conflict?
+
+When faced with a merge conflict, git will mark the problematic area in the file by enclosing it in “<<<<<<<< HEAD” and “>>>>>>>>>>[other branch name]”
+
+The contents after the first marker originate from your current working branch. After the angle brackets, Git tells us where (from which branch) the changes came from. A line with "=======" separates the two conflicting changes.
+Our job is now to clean up these lines: when we're done, the file should look exactly as we want it to look. It is advisable to consult the teammate who wrote the conflicting changes to decide which version should be final. It could be either on of yours - or maybe a mixture between the two.
+
+e.g. :
+```
+ <<<<<<< HEAD:mergetest
+ This is my third line
+ =======
+ This is a fourth line I am adding
+ >>>>>>> 4e2b407f501b68f8588aa645acafffa0224b9b78:mergetest
+```
+
+`<<<<<<<`: Indicates the start of the lines that had a merge conflict. The first set of lines are the lines from the file that you were trying to merge the changes into.  
+`=======`: Indicates the break point used for comparison. Breaks up changes that user has committed (above) to changes coming from merge (below) to visually see the differences.  
+`>>>>>>>`: Indicates the end of the lines that had a merge conflict.  
+
+You resolve a conflict by editing the file and then manually merging the parts of the file that git had trouble merging. This may mean discarding either your changes or someone else's or going ahead with a mix of the two. You will also need to delete the '<<<<<<<', '=======', and '>>>>>>>' in the file.
+
+
+Once you have resolved the conflict do a `git add`. Do not forget to run the tests, as you have to make sure that you have resolved the conflict.
+
+You can also download different plugins depending on the IDE you are using for an easier way to resolve merge conflicts.
+
+
+# How to undo a merge?
+If you want to undo a merge then you can do `git merge —abort`

additional-material/git_workflow_scenarios/reverting-a-commit.md

+# Revert a commit
+
+To revert a commit simply means to create a brand new commit that undoes all
+the changes made in a previous one. It is like doing a ```CTRL + Z ``` on git.
+
+Reversion is made easier in git because every commit you push to your remote repository has a unique alphanumeric key known as SHA(Secure Hash Algorithm) tied to it.
+So this means you can revert any commit as long as you have the SHA.
+But then, you have to be careful to reverse orderly so as not to mess your repository up.
+
+
+To pick out the SHA of the specific commit we want to undo, a log of all the commits we have made so far would come in handy.
+To get this, we would run the command:
+```git log --oneline ```
+Running the ```git log``` command alone would also give us the SHAs (in long form)
+However using the ```--oneline ``` flag tells git that we want it displayed in a concise (one line) manner for easy read.
+
+The first 7 characters displayed when you run this command is called the abbreviated commit hash.
+
+For example, here is what I get when I run ```git log --oneline ``` on this repository:
+```
+389004d added spacing in title
+c1b9fc1 Merge branch 'master' into tutorials
+77eaafd added tutorial for reverting a commit
+```
+
+So this shows that with ```git log --oneline```, we can fetch a list of all the commits made on the repository together with the first 7 characters of its SHA.
+
+Now, Let's assume I want to undo my commit of "added spacing in title", here are the steps I would take:
+
+*   Copy the SHA of the commit which, in this case is ```389004d```
+*   Then, run the command ```git revert 389004d```
+
+This would pop open my text editor and prompt me to edit the commit message.
+You can decide to leave the commit message as the default git message which starts with the word `Revert`
+or you can also decide to customize the message to your liking.
+
+*   Next, I will save and close the text editor.
+*   Return to the command line.
+*   Run ```git push origin <branch-name>``` to push the reverted changes to Github.
+
+And that is it, the change would be undone. In this case,  my repository would be reverted to how it looked like in ```c1b9fc1```