opuppet/puppetlabs-stdlib
4
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Update .travis.yml, Gemfile, Rakefile, and CONTRIBUTING.md

Browse source
This commit is contained in:
Colleen Murphy 2014-12-08 10:33:35 -08:00
parent 4ebea40e08
commit a99971827f
2 changed files with 5 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.travis.yml
View file

@ -1,6 +1,6 @@
--- ---
language: ruby language: ruby
bundler_args: --without development bundler_args: --without system_tests
script: "bundle exec rake validate && bundle exec rake lint && bundle exec rake spec SPEC_OPTS='--color --format documentation'" script: "bundle exec rake validate && bundle exec rake lint && bundle exec rake spec SPEC_OPTS='--color --format documentation'"
matrix: matrix:
fast_finish: true fast_finish: true

22
CONTRIBUTING.md
View file

@ -41,11 +41,9 @@ Checklist (and a short version for the impatient)
* Pre-requisites: * Pre-requisites:
- Sign the [Contributor License Agreement](https://cla.puppetlabs.com/)
- Make sure you have a [GitHub account](https://github.com/join) - Make sure you have a [GitHub account](https://github.com/join)
- [Create a ticket](http://projects.puppetlabs.com/projects/modules/issues/new), or [watch the ticket](http://projects.puppetlabs.com/projects/modules/issues) you are patching for. - [Create a ticket](https://tickets.puppetlabs.com/secure/CreateIssue!default.jspa), or [watch the ticket](https://tickets.puppetlabs.com/browse/) you are patching for.
* Preferred method: * Preferred method:
@ -94,17 +92,7 @@ The long version
whitespace or other "whitespace errors". You can do this by whitespace or other "whitespace errors". You can do this by
running "git diff --check" on your changes before you commit. running "git diff --check" on your changes before you commit.
2. Sign the Contributor License Agreement 2. Sending your patches
Before we can accept your changes, we do need a signed Puppet
Labs Contributor License Agreement (CLA).
You can access the CLA via the [Contributor License Agreement link](https://cla.puppetlabs.com/)
If you have any questions about the CLA, please feel free to
contact Puppet Labs via email at cla-submissions@puppetlabs.com.
3. Sending your patches
To submit your changes via a GitHub pull request, we _highly_ To submit your changes via a GitHub pull request, we _highly_
recommend that you have them on a topic branch, instead of recommend that you have them on a topic branch, instead of
@ -124,7 +112,7 @@ The long version
in order to open a pull request. in order to open a pull request.
4. Update the related GitHub issue. 3. Update the related GitHub issue.
If there is a GitHub issue associated with the change you If there is a GitHub issue associated with the change you
submitted, then you should update the ticket to include the submitted, then you should update the ticket to include the
@ -220,14 +208,12 @@ review.
Additional Resources Additional Resources
==================== ====================
* [Getting additional help](http://projects.puppetlabs.com/projects/puppet/wiki/Getting_Help) * [Getting additional help](http://puppetlabs.com/community/get-help)
* [Writing tests](http://projects.puppetlabs.com/projects/puppet/wiki/Development_Writing_Tests) * [Writing tests](http://projects.puppetlabs.com/projects/puppet/wiki/Development_Writing_Tests)
* [Patchwork](https://patchwork.puppetlabs.com) * [Patchwork](https://patchwork.puppetlabs.com)
* [Contributor License Agreement](https://projects.puppetlabs.com/contributor_licenses/sign)
* [General GitHub documentation](http://help.github.com/) * [General GitHub documentation](http://help.github.com/)
* [GitHub pull request documentation](http://help.github.com/send-pull-requests/) * [GitHub pull request documentation](http://help.github.com/send-pull-requests/)