https://github.com/deni1688/gie
cli tool to create multiple issues for a git provider
https://github.com/deni1688/gie
automation ci cli cli-app git golang issues
Last synced: 3 months ago
JSON representation
cli tool to create multiple issues for a git provider
- Host: GitHub
- URL: https://github.com/deni1688/gie
- Owner: deni1688
- License: mit
- Created: 2022-10-05T09:01:18.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2024-06-17T13:13:55.000Z (about 2 years ago)
- Last Synced: 2025-07-27T12:47:30.342Z (11 months ago)
- Topics: automation, ci, cli, cli-app, git, golang, issues
- Language: Go
- Homepage:
- Size: 4.02 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://github.com/deni1688/gie/actions/workflows/ci.yml)
# gie (git issue extractor)
cli tool to create multiple issues for a git provider
### Overview
This tool should make it simple to extract issues to a git hosting service like GitHub or GitLab from your code base.
Putting extraction one command away will hopefully encourage developers to submit more commits with targeted issues attached. As a result,
tacking different types of changes should become more transparent and measureable.
### How it works
By prefixing comments with a specified tag inside your code and then running `gie` on that file or directory
the comment(s) are extracted, formatted, and submitted to your git hosting service. The resulting issue(s) links are then
appended to the commented line. Each issue will also have a reference to the file where it was extracted from in your git hosting service.
### Example
##### Before
```go
// Issue: Make it possible to do XYZ in refactorMe
func refactorMe() {
// ...
}
```
##### Run
```bash
gie -path .
```
##### After
```go
// Issue: Make it possible to do XYZ refactorMe refactorMe -> closes https://github.com/owner/project/issues/12
func refactorMe() {
// ...
}
```
#### Post issue creation
After the `gie` command is ran it will also check if any webhooks are configured and send all extracted issues to the
configured endpoints.
#### Configuration
The default config file is sourced from your $HOME/.config/gie.json. You can generate this file by running `gie -setup`.
This will create the config json with the following options:
```json
{
"host": "String",
"token": "String",
"prefix": "String",
"query": "String",
"webhooks": "List",
"exclude": "List"
}
```
You can also override the config on each run by providing a path to another json file using the -config flag.
### Roadmap
1. Create a GUI version that can be triggered via a flag which will allow selecting which issues should be created and providing better descriptions.