Quickly answer the question “Why the @*$% does this code exist?”
$ brew tap HeySquirrel/tribe
$ brew install tribe
$ go get -u github.com/HeySquirrel/tribe
$ # Why do these lines of code exist?
$ tribe blame -L100,105 model/user.rb
$ # See basic information about your work items or issues
$ tribe show HIL-78
$ How risky is it to make a change to this file?
$ tribe risk app/models/user.rb
Risk for 'app/models/user.rb'
1 month ago - Last commit
491 - Commit count
7 - Commits last six months
20 - Work items
37 - Contributors
0.99 - Risk
The configuration for tribe is stored in $HOME/.tribe.json. Currently the only configuration is the work item servers you want tribe to understand. Below is an example format.
{
"workitemservers": {
"rally1": {
"type": "rally",
"host": "https://<cool rally server>",
"apikey": "<rally api key here>",
"matcher": "(S|DE|F|s|de|f)[0-9][0-9]+"
},
"myjira": {
"type": "jira",
"host": "https://<cool jira server>",
"username": "<jira username>",
"password": "<jira password>",
"matcher": "HIL-[0-9]+"
}
}
}
You can have as many workitemservers
as you want. Tribe will search through all the servers defined in this section looking for matched work items in your commits.
matcher
for your Rally subscription depends on how your workspaces are setup in Rally. The starting letters of your Artifacts can be changed by your workspace administrator. See above for an example matcher.go test ./...
command and confirm that it passesgofmt -s
:star: this repo to show support. Let us know you liked it on Twitter.