[](https://travis-ci.org/Sam-Lane/Gissue)
[]()
🐙 Github issue manager in the command line
## Installing
##### clone the repository
```bash
$ git clone https://github.com/Sam-Lane/Gissue.git
```
##### install dependencies
```bash
$ pip install -r requirements.txt
```
##### link gissue.py to /usr/local/bin
```bash
$ ln -s $PWD/gissue/gissue.py /usr/local/bin/gissue
```
## Using Gissue
### Authenticating With Github.
Before you can use gissue you need to authenticate with GitHub. Gissue uses Githubs personal access tokens to authenticate and it is super simple to get a token. Simply run:
```bash
$ gissue --generate-token
```
You will then be prompted for your Github username & password.
If your account is secured with oauth this will not work. You will need to go to Github and generate a token in your user settings. Once you have your token run:
```bash
$ gissue --update-token <your token from github here>
```
You should now be authenticated with the Github servers.
### Getting Issues.
#### Inside a directory with a .git folder
When running gissue inside a directory with a ```.git``` directory it will retrieve all issues on the project you are inside.
```bash
$ gissue
(2)🐛 bug - Error when not conected to internet
(1)💉 enhancement - Feature to add issue from cli
```
#### Inside a directory without a .git folder
When running gissue in a directory that does not contain a ```.git``` directory it will retrieve all issues assigned to ***you*** on Github.
### Adding issues
Creating an issue is easy
```bash
$ gissue add
title your issue
> my new issue
```
- gissue will now open your editor defined in the users env variables or default to nano.
- Here you can write the body of your issue. Lines starting with # are ignored. Or leave it blank.
- Save and quit from the editor and your new issue will be posted to github.
```bash
my new issue has been created
```
### Adding issues with labels
You can add issues with one or more labels with the optional ```--label``` argument.
```bash
$ gissue add --label bug
```
You can specify one or more labels from the following labels
[bug, duplicate, enhancement, good first issue, help wanted, invalid, question, hotfix]
### Show the issues in the git repostitory
You can retrieve and print out all the issues in the current repo
```bash
$ gissue show
```
#### Additional Show arguments
There are optional arguments which can be written after the ```show``` command
```bash
$ gissue show --number [number]
```
Retrieves and gets the issue with number/id 1 in the repostitory.
```bash
$ gissue show --state [open, closed, all]
```
Displays issues with the defined state.
## Todo:
- [ ] Add testing suite
- [ ] Add labels to new issue
- [ ] Add comment to existing label
- [ ] Close an issue
- [ ] Open an issue to github website
## Contributors:
- [Erik Lange](https://github.com/eriklange)
Metadata
Release files for gissue 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gissue-0.4.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gissue-0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.5 kB
Release files / gissue-0.4.tar.gz
| Download URL | gissue-0.4.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a76915fc3c795a583b08b95360e04d3e3083fa0063d346a465735e061794994
|
|
BLAKE2b-256 checksum How to use checksums |
49bd3710e3464e26a49a4d8ae82859ea362d17a06348cc931ad2313b79c605ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Release files / gissue-0.4-py3-none-any.whl
| Download URL | gissue-0.4-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d924f93ac352d5af87afc4c2f6075bc5887d0fa962d010b014ecfcf693deb9f7
|
|
BLAKE2b-256 checksum How to use checksums |
66cca915ee77f98e2c59a719bad253fe01c92d467ea9c9dc7308fcf372490795
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Security for gissue 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.