arjunptm / gits Goto Github PK

Add the test case file for the remove functionality.

@ramyasaimullapudi
There is an init.py file missing in our code structure.
As python runs all of the code in the package’s _init.py file, all of the objects defined in the module or the package’s _init.py file will be then made available to the importer.
Can you please try to add init file in order for the test files to detect the corresponding classes.

Need to check how to fetch the current python version installed

@arjunptm, as the gitID is yours, only you are authorized to create a zenodo badge. Please create the badge and comment on the URL so I can add it to readME.md. This is part of #7

There seem to be many branches that have been merged . As a housekeeping task, we can clean up those branches.

Deleting the branch itself would however remove valuable information, so we can try to archive it using the method listed in this thread:
https://stackoverflow.com/questions/1307114/how-can-i-archive-git-branches

Use a format for all the docstrings for functions.

There seem to be many old branches that the previous teams used, but I doubt they'll be functional anymore. As a housekeeping task, we can clean up those branches.

Deleting the branch itself would however remove valuable information, so we can try to archive it using the method listed in this thread:
https://stackoverflow.com/questions/1307114/how-can-i-archive-git-branches

I'm assigning two people on this since there seem to be a lot of branches, even though it should be a quick task.

I think the code coverage is evaluating for both code/ and test/ because of which it is showing as 45%. We might need to change the path to codecov(not sure)

Error: Import is not being handled properly.
Changes are to be done in:
1.test_checkout.py
2.test_gits_add.py
3.test_gits_all_branch.py
4.test_gits_commit.py
5.test_gits_create_branch.py
6.test_gits_diff.py
7.test_gets_init.py
8.test_gets_remote_branch.py
9.test_gets_status.py
10.test_unstage.py.
@ramyasaimullapudi Can you please handle the 6-10 files, I will do the rest.

This can mean some sort of command-line interaction where the program waits for user input during execution, in a conversational manner.

The current Readme does not show how to use GITS with examples.

Since we have forked this project, we may need to set up all the integrations once more: the Travis CI, Codecov, etc. Basically, run through all the badges on the readme and check if anything needs updating. Since @ramyasaimullapudi did this for the previous project, do you think you can take this over too?

@arjunptm You are only authorized to connect codecov to it. Please add it to the project. This is part of #7

Each gits command has a set of lines associated with it in gits.py. Some of them are not using appropriate variable names, so change each to match their functionalities.

https://github.com/txt/se21/blob/master/docs/proj1rubric.md

• Add a detailed explanation to the readme.
• Re-order the features listed in a sensible manner
• Add examples on how to run/use each feature

Requirement: Implementation of "gits mv" command:
Moves the file, updating the index to record the replaced file path, as well as updating any affected git submodules.

Requirement: Implementation of "gits rm" command:
git-rm - Remove files from the working tree and from the index.

Right now, the project can be run by cloning the repository.

Creating an executable will help non-developer users also experience the thrill and joy of using GITS for their personal as well as professional work.

This is a bug, pr_update should have a separate command to run. Look for reasonable changes to make and fix this issue.

For python3 only users, getting this issue on running source ~/.bash_rc.
It might be because of the fact that Linux defaults to Python 2 or something incompatible with pathlib.
Traceback (most recent call last):
File "gits_logging.py", line 3, in
from pathlib import Path
ImportError: No module named pathlib

The repository is set up to run unit tests after every pull request or code push.

Updating the gits commit command to run tests locally before creating a commit will save any failing builds from being pushed to the repository itself.

Look into existing GITS functionalities, and try to list out features that can be added here.

Create a GITS feature that can do the following:

1. Check for existing SSH keys
2. Create an SSH key pair for a new email address
3. Add ssh key to ssh-agent
4. copy the public key to clipboard to easily paste into github.