| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Update code of conduct tenplate to CC2.0 | Coraline Ada Ehmke | 2020-02-16 | 1 | -47/+57 |
| | | |||||
| * | Fix comments and messages to refer to https url | Takayuki Nakata | 2019-08-21 | 1 | -3/+3 |
| | | |||||
| * | Upgrade template Code of Conduct to Covenant 1.4 | Sean Collins | 2016-03-04 | 1 | -29/+54 |
| | | |||||
| * | Updates Contributor Covenant to 1.3.0 | CoralineAda | 2015-11-24 | 1 | -12/+39 |
| | | | | The code of conduct template also now inserts email address for contact purposes. | ||||
| * | Update code of conduct to Contributor Covenant version 1.2.0update-code-of-conduct | Erik Michaels-Ober | 2015-08-04 | 1 | -24/+15 |
| | | |||||
| * | update generated CoC to Contributor Covenant v1.1 | Andre Arko | 2015-06-25 | 1 | -7/+25 |
| | | | | | h/t @strand @coralineada | ||||
| * | Update CODE_OF_CONDUCT.md.tt | Andrey Korobkov | 2015-04-23 | 1 | -1/+1 |
| | | | | "Ethnicity" was missed from discriminations list (see original version at http://contributor-covenant.org/version/1/0/0/code_of_conduct.md) | ||||
| * | Fix URL for Contributer Covenant | Faraz Yashar | 2015-03-20 | 1 | -1/+1 |
| | | | | Forward slashes were missing. | ||||
| * | Extended gem generation and generation settings | Kir Shatrov | 2015-01-25 | 1 | -0/+13 |
| | | | | | | | | | | | | | | As discussed in https://github.com/bundler/bundler/pull/3305#issuecomment-67024669, the gem generator should not generate default files that change the rights or responsibilities of gem authors without their explicit consent. Let's change the gem generator to ask gem authors what they want, and allow them to change it via config or --flags. * Remove LICENSE from default gem * Remove CODE_OF_CONDUCT from default gem * Add --coc flag to generate CODE_OF_CONDUCT * Add --mit flag to generate LICENSE * On gem generation, if not set to true/false, ask user if they are willing to license their code permissively under the MIT license * On gem generation, if not set to true/false, ask user if they are willing to add a Code of Conduct to their gem * On gem generation, if not set to false/rspec/minitest, ask if the user would like to generate tests along with their gems. Save the answer as bundle config gem.tests. * Ensure that --coc, --mit, --test flags overrule any config settings that may be set. | ||||
| * | Revert "Merge pull request #3305 from doodzik/master" | Tim Moore | 2014-12-16 | 1 | -13/+0 |
| | | | | | | | | | | | | | | | | This reverts commit 8677640f3375794898d17b47cee1d7276c4c1515, reversing changes made to edcfb5718c27b85e202bcfa6934580be704ff3ee. Conflicts: lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt This follows further discussion in https://github.com/bundler/bundler/pull/3305 where it was pointed out that adding this to gems without the maintainers' explicit consent and committment to enforcement is dangerous and counter-productive. A more thorough approach is planned in https://trello.com/c/1349U0gF | ||||
| * | Fix typo spotted by @schneems [ci skip] | Zachary Scott | 2014-12-14 | 1 | -1/+1 |
| | | |||||
| * | add code of conduct when scaffolding a gem | doodzik | 2014-12-13 | 1 | -0/+13 |
 |
index : delta/bundler.git | |
| github.com: bundler/bundler.git |
| summaryrefslogtreecommitdiff |