krank
krank copied to clipboard
guibou
Krank checks your code source comments for important markers
Right now the setting of credentials is done using cli argument. We can improve that by using environment variables. I propose to use `KRANK_GITHUB_TOKEN=token`, as well as `KRANK_GITLAB_TOKENS=gitabhost=token;gitlabhost2=token2` cc @zimbatm...
For now we have only one important option: `--issuetracker-githubkey`, but in a near future (when #33 will be merged) we'll have also a similar option for gitlab. We can also...
Right now we designed `ignore` so a closed bug does not trigger an error. I think we should rework it so now an open bug triggers an error. I see...
`krank` performances highly depends on the performance of the regular expression we use to find issues. We need to setup a performance regression test, but I don't know how.
It may be cool to have the output in a computer readable format (JSON?).
Urls such as: `https://ghc.haskell.org/trac/ghc/ticket/11744`
Jira issues looks like `https://PROJECT.atlassian.net/browse/[A-Z]+-[0-9]+`
krank command line may now have a lot of options (such as all the api key needed for github and gitlab instances) which are painful to set to each call,...