amolgautam25 · urvishvasani · Oct 1, 2020 · Oct 1, 2020 · Oct 3, 2020 · Oct 3, 2020
diff --git a/.coverage b/.coverage
diff --git a/.gitignore b/.gitignore
@@ -1,10 +1,13 @@
-# Binaries for programs and plugins
+#Binaries for programs and plugins
 *.exe
 *.exe~
 *.dll
 *.so
 *.dylib
 
+# GITS.egg-info
+GITS.egg-info/
+dist/
 # Test binary, built with `go test -c`
 *.test
 
@@ -45,6 +48,7 @@ luac.out
 /test/tmp/
 /test/version_tmp/
 /tmp/
+/.idea/
 
 # Used by dotenv library to load environment variables.
 # .env

diff --git a/.tmux.conf b/.tmux.conf
@@ -0,0 +1,67 @@
+set -g aggressive-resize on
+set-option -g default-shell /usr/bin/fish
+unbind C-b
+set -g prefix C-space
+bind C-space send-prefix
+set -g base-index 1
+# start with pane 1
+bind | split-window -h -c "#{pane_current_path}"
+bind - split-window -v -c "#{pane_current_path}"
+unbind '"'
+unbind %
+# open new windows in the current path
+bind c new-window -c "#{pane_current_path}"
+# reload config file
+bind r source-file $Tnix/.config/dottmux
+unbind p
+bind p previous-window
+# shorten command delay
+set -sg escape-time 1
+# don't rename windows automatically
+set-option -g allow-rename off
+# mouse control (clickable windows, panes, resizable panes)
+set -g mouse on
+# Use Alt-arrow keys without prefix key to switch panes
+bind -n M-Left select-pane -L
+bind -n M-Right select-pane -R
+bind -n M-Up select-pane -U
+bind -n M-Down select-pane -D
+# enable vi mode keys
+set-window-option -g mode-keys vi
+# set default terminal mode to 256 colors
+set -g default-terminal "screen-256color"
+bind-key u capture-pane \;\
+    save-buffer /tmp/tmux-buffer \;\
+    split-window -l 10 "urlview /tmp/tmux-buffer"
+bind P paste-buffer
+bind-key -T copy-mode-vi v send-keys -X begin-selection
+bind-key -T copy-mode-vi y send-keys -X copy-selection
+bind-key -T copy-mode-vi r send-keys -X rectangle-toggle
+# loud or quiet?
+set-option -g visual-activity off
+set-option -g visual-bell off
+set-option -g visual-silence off
+set-window-option -g monitor-activity off
+set-option -g bell-action none
+#  modes
+setw -g clock-mode-colour colour5
+# panes
+# statusbar
+set -g status-position top
+set -g status-justify left
+set -g status-bg colour232
+set -g status-fg colour137
+###set -g status-attr dim
+set -g status-left ''
+set -g status-right '#{?window_zoomed_flag,🔍,} #[fg=colour255,bold]#H #[fg=colour255,bg=colour19,bold] %b %d #[fg=colour255,bg=colour8,bold] %H:%M '
+set -g status-right '#{?window_zoomed_flag,🔍,} #[fg=colour255,bold]#H %H:%M '
+set -g status-right-length 50
+set -g status-left-length 20
+setw -g window-status-current-format ' #I#[fg=colour249]:#[fg=colour255]#W#[fg=colour249]#F '
+setw -g window-status-format ' #I#[fg=colour237]:#[fg=colour250]#W#[fg=colour244]#F '
+
+# messages
+# layouts
+bind S source-file $Tnix/.config/tmux-session1
+setw -g monitor-activity on
+set -g visual-activity on
diff --git a/.travis.yml b/.travis.yml
@@ -1,9 +1,20 @@
-language: python
+
+language:
+  python
 python:
-  - "3.8"      # current default Python on Travis CI
-# command to install dependencies
-#install:
-#  - pip install -r requirements.txt
-# command to run tests
+ - "3.5"
+install:
+ - pip install -U pip
+ - pip install -r requirements.txt
+ - pip install coverage
+ - pip install codecov
+git:
+  depth: 50
+jobs:
+  include:
+  - name: "project-1"
+    python: "3.8"
 script:
-  - python3 -m pytest
+  - coverage run -m pytest -q test/
+after_success:
+  - bash <(curl -s https://codecov.io/bash) -t d9ad46a5-ddae-4e9b-b0db-959bb96541f0
diff --git a/PROJ1-selfAssessment.md → PROJ2-selfAssessment.md b/PROJ1-selfAssessment.md → PROJ2-selfAssessment.md
@@ -3,10 +3,10 @@
 |Misc | Group members attended tutorial sessions|4|
 |Distrbuted dev model: | decisions made by unanmyous vote}|4|
 || group meetings had a round robin speaking order|4|
-|| group meetings had a moderator that managed the round robin|2|
-|| group meeting moderator rotated among  the group|2|
+|| group meetings had a moderator that managed the round robin|4|
+|| group meeting moderator rotated among  the group|4|
 || code conforms to some packaging standard|4|
-|| code has can be downloaded from some standard package manager|0|
+|| code has can be downloaded from some standard package manager||
 | |workload is spread over the whole team (one team member is often Xtimes more productive than the others... but nevertheless, here is a track record that everyone is contributing a lot)|4|
 || Number of commits|4|
 || Number of commits: by different people|4|
@@ -15,11 +15,11 @@
 || License: exists|4|
 || DOI badge: exists |4|
 ||Docs: doco generated , format not ugly |4|
-||Docs: what: point descriptions of each class/function (in isolation) |4|
-||Docs: how: for common use cases X,Y,Z mini-tutorials showing worked examples on how to do X,Y,Z|2|
-||Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush out and use the thing|4|
+||Docs: what: point descriptions of each class/function (in isolation) ||
+||Docs: how: for common use cases X,Y,Z mini-tutorials showing worked examples on how to do X,Y,Z||
+||Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush out and use the thing||
 ||Docs: 3 minute video, posted to YouTube. That convinces people why they want to work on your code.|4|
-|| (hard) code conforms to some known patterns |2|
+|| (hard) code conforms to some known patterns ||
 |Tools Matter| Use of version control tools|4|
 || Extensive use of version control tools |4|
 || Repo has an up-to-date requirements.txt file|4|
@@ -30,22 +30,22 @@
 || Extensive Use of code  formatters. |4|
 || Use of syntax checkers. |4|
 || Extensive use of syntax checkers. |4|
-|| Use of code coverage |2|
-|| Extensive use of code coverage |2|
-|| other automated analysis tools|2|
-|| Extensive use of  other automated analysis tools|2|
+|| Use of code coverage |4|
+|| Extensive use of code coverage |4|
+|| other automated analysis tools||
+|| Extensive use of  other automated analysis tools||
 || test cases exist|4|
 || test cases are routinely executed|4|
-| consensus-oriented model| the files CONTRIBUTING.md and CODEOFCONDUCT.md has have multiple edits by multiple people|4|
-| | the files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up|4|
+| consensus-oriented model| the files CONTRIBUTING.md and CODEOFCONDUCT.md has have multiple edits by multiple people||
+| | the files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up||
 | | multiple people contribute to discussions|4|
 || issues are discussed before they are closed|4|
 || Chat channel: exists|4|
 || Chat channel: is active |4|
-|| test cases:.a large proportion of the issues related to handling failing cases.|2|
-| zero internal boundaries | evidence that the whole team is using the same tools: everyone can get to all tools and files|4|
-| | evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people)|4|
-| | evidence that the whole team is using the same tools (e.g. tutor can ask anyone to share screen, they demonstrate the system running on their computer)|4|
-| | evidence that the members of the team are working across multiple places in the code base|4|
-| low-regressions rule | (hard to judge) features released are not subsequently removed|4|
-|short release cycles | (hard to see in short projects) project members are committing often enough so that everyone can get your work|4|
+|| test cases:.a large proportion of the issues related to handling failing cases.||
+| zero internal boundaries | evidence that the whole team is using the same tools: everyone can get to all tools and files||
+| | evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people)||
+| | evidence that the whole team is using the same tools (e.g. tutor can ask anyone to share screen, they demonstrate the system running on their computer)||
+| | evidence that the members of the team are working across multiple places in the code base||
+| low-regressions rule | (hard to judge) features released are not subsequently removed||
+|short release cycles | (hard to see in short projects) project members are committing often enough so that everyone can get your work||
diff --git a/README.md b/README.md
@@ -2,76 +2,83 @@
 # GITS 
 ### GIT Simplified
 
-![GitHub](https://img.shields.io/github/license/amolgautam25/GITS)
-[![Build Status](https://travis-ci.com/amolgautam25/GITS.svg?branch=master)](https://travis-ci.com/amolgautam25/GITS)
-![GitHub](https://img.shields.io/badge/language-python-blue.svg)
-![GitHub](https://img.shields.io/badge/language-shell-orange.svg)
-![YouTube Video Views](https://img.shields.io/youtube/views/cMcftHMtIZ4?style=social)
+![GitHub](https://img.shields.io/github/license/harshitpatel96/GITS)
+[![Build Status](https://travis-ci.com/harshitpatel96/GITS.svg?branch=master)](https://travis-ci.com/harshitpatel96/GITS)
+[![codecov](https://codecov.io/gh/harshitpatel96/GITS/branch/master/graph/badge.svg?token=G6RG52G2YO)](https://codecov.io/gh/harshitpatel96/GITS/)
+![YouTube Video Views](https://img.shields.io/youtube/views/6Y8_RQecnZ8?style=social)
 
 [![DOI](https://zenodo.org/badge/295480790.svg)](https://zenodo.org/badge/latestdoi/295480790)
 
-![GitHub issues](https://img.shields.io/github/issues/amolgautam25/GITS)
-![GitHub closed issues](https://img.shields.io/github/issues-closed/amolgautam25/GITS)
-
-![GitHub pull requests](https://img.shields.io/github/issues-pr/amolgautam25/GITS)
-![GitHub closed pull requests](https://img.shields.io/github/issues-pr-closed/amolgautam25/GITS)
-
-[![](https://img.youtube.com/vi/cMcftHMtIZ4/0.jpg)](https://youtu.be/cMcftHMtIZ4 "GITS demo")
-
-
-### Supported functionality
-
-#### gits pr_update
-This functionality makes sure that the current branch is able to make a PR without much trouble ( conflict ). It makes sure that the current branch has the latest commit off master branch, and that the local master has all the commits from the upstream master. This helps in reducing merge conflicts
-
-#### gits profile
-This functionality allows the user to change the git account quickly with a single command. There are situations when a developer has a personal github account and a enterprise github account as well. Changing between these accounts is a little complicated. This functionality aims to simplify it.
-
-#### gits rebase 
-This is a highly simplified version of git rebase command. This interactive command asks for the branch that you want to rebase and automatically rebases it off master. This is the most common scenario. The original GIT rebase command is a little un-intuitive and there is always a confusion , about the source branch and the destination branch.  
-
-#### gits reset
-'Reset' intuitively means a HARD reset. This functionality does a HARD reset on your branch, and makes it even with the remote branch. This aims to simplify the confusion between HARD and the SOFT reset.  
-
-#### gits set
-This functionality sets the parent branch. 
-
-#### gits upstream
-This functionality changes the upstream with a single command. No need to manually remove the existing upstream, and adding a new upstream. This command will automatically change the upstream for the git repo. If there is any existing upstream , it will be overwritten.
-
-#### gits super reset
-Have you ever run into a situation, where you had to clone the repository again ? Yes, this functionality is exactly for that scenario. It will remove the current repository. It will clone it again, and add all the 'remote' to this freshly cloned repository. 
-
-#### gits add 
-Function that adds files as passed to the gits add command. Performs operation as similar to git add command
-
-#### gits commit
-It is a highly simplified version of git commit command. We are actively working on this functionality such that a commit would fail if the unit tests does not pass. We can specify the tests that need to pass before the commit can actually happen. 
-
-#### gits create_branch
-This automatically checks out a new branch from local master , after pulling all the changes from the remote master to local master. The idea behind this is that this new branch should have all the latest commits before a developer starts working on them.
-
-#### gits logging
-This logs all the commands executed by the user, and also stores the output of each command
-
-Note: More functionality are being added to this project. Please refer to the 'issues' tab for more information. In case you want to contribute to this project , please refer to 'Contributing.md' file.
-
-
-### pydoc implementation
+![GitHub issues](https://img.shields.io/github/issues/harshitpatel96/GITS)
+![GitHub closed issues](https://img.shields.io/github/issues-closed/harshitpatel96/GITS)
+
+[![](https://img.youtube.com/vi/6Y8_RQecnZ8/hqdefault.jpg)](https://youtu.be/6Y8_RQecnZ8 "GITS demo")
+
+# About GITS
+GITS streamlines most frequently performed workflows using fewer commands which is so much easier and better than usual.
+Git-Simplified AKA GITS can be thought of wrapper around major Git functionalities.
+
+# Installation for Linux
+1. Clone GITS Repo
+2. From the root directory run the following command
+    ```
+    pip install -r requirements.txt
+    ```
+3. Go to configurations directory and run the following command
+    ```
+    bash project_init.sh
+    ```
+
+# Installation for Windows
+1. Clone GITS Repo
+2. From the root directory run the following command
+    ```
+    pip install -r requirements.txt
+    ```
+3. Currently, this project cannot be run on Windows. You need to make use of WSL to work on this project in Windows 
+although this fix would only work for systems running Windows 10. If you are using another version of Windows, using a 
+virtual machine might be preferred.
+
+    Please refer this link to enable WSL : https://docs.microsoft.com/en-us/windows/wsl/install-win10
+
+# How to Contribute?
+Please take a look at our CONTRIBUTING.md where we provide instructions on contributing to the repo and help us in enhancing the current video conferencing platforms.
+
+# Documentation
+## Functionalities Implemented
+1. [gits profile](https://github.com/harshitpatel96/GITS/blob/master/docs/profile.md)
+1. [gits rebase](https://github.com/harshitpatel96/GITS/blob/master/docs/rebase.md)
+1. [gits reset](https://github.com/harshitpatel96/GITS/blob/master/docs/reset.md)
+1. [gits upstream](https://github.com/harshitpatel96/GITS/blob/master/docs/upstream.md)
+1. [gits super reset](https://github.com/harshitpatel96/GITS/blob/master/docs/super_reset.md)
+1. [gits commit](https://github.com/harshitpatel96/GITS/blob/master/docs/commit.md)
+1. [gits create_branch](https://github.com/harshitpatel96/GITS/blob/master/docs/create_branch.md)
+1. [gits logging](https://github.com/harshitpatel96/GITS/blob/master/docs/logging.md)
+1. [gits undo](https://github.com/harshitpatel96/GITS/blob/master/docs/undo.md)
+1. [gits untrack](https://github.com/harshitpatel96/GITS/blob/master/docs/untrack.md)
+1. [gits track](https://github.com/harshitpatel96/GITS/blob/master/docs/track.md)
+1. [gits delete](https://github.com/harshitpatel96/GITS/blob/master/docs/delete.md)
+1. [gits sync](https://github.com/harshitpatel96/GITS/blob/master/docs/sync.md)
+1. [gits switch](https://github.com/harshitpatel96/GITS/blob/master/docs/switch.md)
+1. [gits status](https://github.com/harshitpatel96/GITS/blob/master/docs/status.md)
+1. [gits branch](https://github.com/harshitpatel96/GITS/blob/master/docs/branch.md)
+1. [gits diff](https://github.com/harshitpatel96/GITS/blob/master/docs/diff.md)
+1. [gits init](https://github.com/harshitpatel96/GITS/blob/master/docs/init.md)
+1. [gits merge](https://github.com/harshitpatel96/GITS/blob/master/docs/merge.md)
+1. [gits push](https://github.com/harshitpatel96/GITS/blob/master/docs/push.md)
+1. [gits pull](https://github.com/harshitpatel96/GITS/blob/master/docs/pull.md)
+
+
+## Pydoc implementation
 We have tried to write as much documentation as possible. You can use pydoc to go through the documentation. 
 For example if you want to go through all the documentation for all files in code/ directory, do the following: 
 
 `cd code`<br>
 `python3 -m pydoc -b `
 
-This will open up a browser and you can see all the files. You can click on a particular file to access the documentation associated with that file.
+This will open up a browser and you can see all the files. You can click on a particular file to access the 
+documentation associated with that file.
 
 This repository is made for CSC 510 Software Engineering Course at NC State University.
 
-Group 17 Team Members: 
 
-Amol Gautam  
-Sneha Kumar  
-Sreeraksha Mavinhally Sreekantha  
-Srujana Rachakonda  
-Tanay Agarwal