Many formatting updates (#27)

* Many formatting updates

* Fixed broken links

* Fixed links

* Fixed links v2

* Fixed links v3

* Fixed links v4

* Fixed links v5

* Fixed links v6

Author: palisadoes

docs/git-guide/Git working/Stage changes/stage-additions.md

@@ -1,10 +1,14 @@
-# Work on a feature branch
+---
+title: Work on a feature branch
+id: feature
+sidebar_position: 3
+---
 
 Working with git can be organized by creating a branch for each issue or feature.Git is designed for lightweight branching and merging. You can and should create as many branches as you’d like.
 
 First, make sure your `develop` branch is up-to-date with Talawa upstream. [(see how)](#keep-your-fork-up-to-date)
 
-Next from your `develop` branch,create a new branch. We recommend naming your branch a descriptive name relating to your feature or issue. 
+Next from your `develop` branch,create a new branch. We recommend naming your branch a descriptive name relating to your feature or issue.
 
 ```
 $ git checkout develop
@@ -13,4 +17,4 @@ $ git checkout -b issue-178-docsissue
 Switched to a new branch 'issue-178-docsissue'
 ```
 
-Now you are ready to work on the issue or feature. 
+Now you are ready to work on the issue or feature.

docs/git-guide/Git working/Stage changes/stage-deletions.md

@@ -1,4 +1,8 @@
-# Keep your fork up to date
+---
+title: Keep your fork up to date
+id: fork
+sidebar_position: 2
+---
 
 You'll want to [keep your fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) up-to-date with changes from Talawa's main repositories
 
@@ -14,4 +18,4 @@ Next is pulling the upstream and [pushing the changes](https://docs.github.com/e
 ```
 $ git pull upstream develop
 $ git push origin develop
-```
+```

docs/git-guide/Git working/branch.md

@@ -1,6 +1,10 @@
-# Using Git as you work
+---
+title: Introduction
+id: introduction
+sidebar_position: 1
+---
 
-## Know what branch you're currently working on 
+## Know what branch you're currently working on
 
 When working with Git, it's crucial to know which branch you have currently checked out, Most of the Git commands implicitly operate on the current branch. you can determine the currently checked out branch in several ways:
 
@@ -20,7 +24,7 @@ $ git branch
   main
 ```
 
-You can see more detailed information about your branches, including remote branches, to do the same use, ```git branch -vva```
+You can see more detailed information about your branches, including remote branches, to do the same use, `git branch -vva`
 
 ```
 $ git branch -vva

docs/git-guide/Workingcopies/usefulgitcommands.md

@@ -1,4 +1,8 @@
-# Stage changes
+---
+title: Introduction
+id: introduction
+sidebar_position: 1
+---
 
 Files in Git can have three possible states: committed, modified, and staged.
 

docs/git-guide/Workingcopies/workflows.md

@@ -0,0 +1,44 @@
+---
+title: Stage Changes with git add
+id: stage-additions
+sidebar_position: 3
+---
+
+To add changes to your staging area, use `git add <filename>`. Because `git add` is all about staging the changes you want to commit, you use it to add new files as well as files with changes to your staging area.
+
+Continuing our above example, after we run `git add docs/introduction.md`, we'll see the following from `git status`:
+
+```
+
+On branch issue-178-docsissue
+Changes to be committed:
+  (use "git reset HEAD <file>..." to unstage)
+
+  new file:  docs/introduction.md
+
+```
+
+You can view the changes in files you have staged with `git diff --cached`. To view changes to files you haven’t yet staged, just `use git diff`.
+
+If you want to add all changes in the working directory, `use git add -A` [(documentation)](https://git-scm.com/docs/git-add).
+
+If you stage a file, you can undo it with `git reset HEAD <filename>`. Here’s an example where we stage a file `test2.md` and then unstage it:
+
+```
+$ git add test2.md
+On branch issue-234
+Changes to be commited:
+   (use "git reset HEAD <file>..." to unstage)
+
+   new file: test2.md
+
+$ git reset HEAD test2.md
+$ git status
+On branch issue-234
+Untracked files:
+   (use "git add <file>..." to include in what will be commited)
+
+   test2.md
+
+nothing added to commit but untracked files present (use "git add" to track)
+```

docs/git-guide/Workingcopies/workingcopies.md

@@ -0,0 +1,33 @@
+---
+title: Stage Changes with git rm
+id: stage-deletions
+sidebar_position: 4
+---
+
+To remove existing files from your repository, use `git rm` [documentation](https://git-scm.com/docs/git-rm). This command can either stage the file for removal from your repository AND delete it from your working directory or just stage the file for deletion and leave it in your working directory.
+
+To stage a file for deletion and remove it from your working directory, `use git rm <filename>`:
+
+```
+$ git rm --cached test4.md
+rm 'test4.md'
+
+$ git status
+On branch issue-100
+Changes to be commited:
+   (use "git reset HEAD <file>..." to unstage)
+
+   deleted: test4.md
+
+$ ls test4.md
+test4.md
+
+```
+
+If you stage a file for deletion with the `--cached option`, and haven’t yet run `git commit`, you can undo it with `git reset HEAD <filename>`:
+
+```
+$ git reset HEAD test4.md
+```
+
+Unfortunately, you can’t restore a file deleted with `git rm` if you didn’t use the `--cache` option. However, `git rm` only deletes files it knows about. Files you have never added to Git won’t be deleted.

docs/git-guide/Git working/commit-changes.md renamed to docs/git-guide/git-workflow/finish/commit-changes.md

@@ -1,6 +1,10 @@
-# Get status of working directory
+---
+title: Get status of working directory
+id: get-status
+sidebar_position: 2
+---
 
-To see what files in the working directory have changes that have not been staged, use ```git status```.
+To see what files in the working directory have changes that have not been staged, use `git status`.
 
 If you have no changes in the working directory, you’ll see something like this:
 
@@ -16,8 +20,8 @@ If you have unstaged changes, you’ll see something like this:
 On branch issue-178-docsissue
 Untracked files:
   (use "git add <file>..." to include in what will be committed)
-  
+
   docs/introduction.md
 
-nothing added to commit but untracked files present (use "git add" to track)  
-```
+nothing added to commit but untracked files present (use "git add" to track)
+```

docs/git-guide/Git working/push-commits.md renamed to docs/git-guide/git-workflow/finish/push-commits.md

@@ -1,4 +1,8 @@
-# Collaborate
+---
+id: collaborate
+title: Collaborate
+sidebar_position: 5
+---
 
 ## Fetching work of other Contributors
 
@@ -37,4 +41,4 @@ Now switch to the branch
 $ git checkout BRANCHNAME
 ```
 
-Now you can work on this branch as you normally work in other branch.
+Now you can work on this branch as you normally work in other branch.

docs/git-guide/Git working/Feature-branch.md renamed to docs/git-guide/git-workflow/setup/feature-branch.md

@@ -1,6 +1,7 @@
 ---
 id: get-the-code
 title: Get The Code
+sidebar_position: 3
 ---
 
 Each of our projects use a **forked-repo** and **merge-oriented** workflow. This means all contributors create a fork of the repository they want to contribute to and then submit pull requests to the upstream repository to have their contributions reviewed and accepted. We also recommend you work on feature branches.