issues
search
hinnefe2
/
gitrisky
Predict code bug risk with git metadata
MIT License
42
stars
15
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Fatal: no such path error within git blame subprocesss
#23
mhyeonsoo
opened
3 years ago
0
Can git meta data be used to detect risk factors or vulnerabilities in the code
#22
mannixm
opened
4 years ago
0
Bump version to 0.1.3
#21
hinnefe2
closed
4 years ago
0
Update travis badge to match travis-ci.com migration
#20
hinnefe2
closed
4 years ago
0
Fail model training step when no bug fix commits found
#19
hinnefe2
closed
4 years ago
0
Group the git diff header
#18
LunaQ
opened
5 years ago
0
Running gitrisky predict throws error ValueError: need more than 1 value to unpack
#17
Phillipe-Bojorquez
closed
4 years ago
2
Option to use custom bug fix pattern
#16
nm17
opened
6 years ago
2
Add cli tests
#15
hinnefe2
closed
6 years ago
0
Refactor feature generation
#14
hinnefe2
opened
6 years ago
0
Add model.py tests
#13
hinnefe2
closed
6 years ago
0
DOC Add hasbadges badge to README
#12
hinnefe2
closed
6 years ago
0
Add tests for gitcmds.py
#11
hinnefe2
closed
6 years ago
0
Write readme
#10
hinnefe2
closed
6 years ago
0
Add verbose option to generate more logging
#9
hinnefe2
opened
6 years ago
2
Add one-hot encoded string features
#8
hinnefe2
opened
6 years ago
0
Add python version classifiers
#7
hinnefe2
closed
6 years ago
0
App crashes at launch
#6
nm17
closed
6 years ago
1
Bugfix merge tag
#5
hinnefe2
closed
6 years ago
0
Prep for pypi
#4
hinnefe2
closed
6 years ago
0
Add setup.py file
#3
hinnefe2
closed
6 years ago
0
Add code coverage step to travis.yml
#2
hinnefe2
closed
6 years ago
1
Connect to travis ci
#1
hinnefe2
closed
6 years ago
0