Project

pain

0.0
Low commit activity in last 3 years
A long-lived project that still receives updates
painanicholson/painHomepageDocumentationSource CodeBug TrackerWiki
Based on http://www.lostgarden.com/2008/05/improving-bug-triage-with-user-pain.html
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
11,612
Stars
0
Forks
0
Watchers
2
 Releases
Current version
0.2.0
Total releases
6
First release
2014-05-07
Latest release
2024-11-04
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
0
Merged Pull Requests
1
Pull Request Acceptance Rate
100%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2019-03-02
Reverse Dependencies
0

 Dependencies

Development

bundler
~> 2.5
pry
>= 0
rake
>= 0
simplecov
>= 0
simplecov-rcov
>= 0
rspec
< 4
rubygems-update
>= 0

Runtime

term-ansicolor
~> 1.11
 Project Readme

Pain

Quickly gauge the User Pain a bug will cause. Basically stolen from http://www.lostgarden.com/2008/05/improving-bug-triage-with-user-pain.html

Code Climate

Installation

Install it yourself as:

$ gem install pain

Usage

Usage: pain [options]
    -l, --likelihood [LIKELIHOOD]    How likely is this bug to occur?
    -i, --impact [IMPACT]            How much impact will this bug have?
    -t, --type [TYPE]                What kind of bug is this?

Contributing

  1. Fork it ( https://github.com/anicholson/pain/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request