| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Use the `changelog` namespace for Rake tasks | Tom Duffield | 2016-11-09 | 1 | -22/+21 |
| | | | | | Signed-off-by: Tom Duffield <tom@chef.io> | ||||
| * | Add gem release badge to the readme / changelog header (#5527) | Tim Smith | 2016-11-08 | 1 | -0/+1 |
| | | | | | | When we update our changelog it’s a bit confusing since multiple days go by before we ship the new release. Adding a header to the changelog and a readme gem release badge should help clear up what our current release actually is. Signed-off-by: Tim Smith <tsmith@chef.io> | ||||
| * | Update changelog generator to better fill our pattern (#5515) | Tom Duffield | 2016-11-04 | 1 | -2/+19 |
| | | | | | | | | | | | | | | | | | | | | | | * Update changelog generator to better fill our pattern Configure the changelog generator to better fit our current pattern of changelogs. By utilizing the HISTORY.md file, we can generate a combined changelog of the latest version from HISTORY.md to now. Then, when we cut a release we can simply move our current changelog into HISTORY.md (using the appropriate rake task) and start the process over again. This might even be a first step to having the Chef Versioner generate the changelog automatically for us each time it bumps the version, and then we just need to groom it as we go along. Signed-off-by: Tom Duffield <tom@chef.io> * Add HISTORY.md for the 12.15.19 release Signed-off-by: Tom Duffield <tom@chef.io> | ||||
| * | remove issues from changelog generator | Lamont Granquist | 2016-05-11 | 1 | -0/+1 |
| | | |||||
| * | Simplify external tests and make them work with Gemfile.lock | John Keiser | 2016-04-18 | 1 | -0/+12 |
 |
index : delta/ruby-gems/chef.git | |
| github.com: opscode/chef.git |
| summaryrefslogtreecommitdiff |