Contributing to Google Cloud Stackdriver
- Sign one of the contributor license agreements below.
- Fork the repo, develop and test your code changes.
- Send a pull request.
Contributor License Agreements
Before we can accept your pull requests you'll need to sign a Contributor License Agreement (CLA):
- If you are an individual writing original source code and you own the intellectual property, then you'll need to sign an individual CLA.
- If you work for a company that wants to allow you to contribute your work, then you'll need to sign a corporate CLA.
You can sign these electronically (just scroll to the bottom). After that, we'll be able to accept your pull requests.
In order to use the stackdriver console and run the project's tests, there is a small amount of setup:
Install Ruby. stackdriver requires Ruby 2.5+. You may choose to manage your Ruby and gem installations with RVM, rbenv, or chruby.
$ gem install bundler
- Install the top-level project dependencies.
$ bundle install
- Install the Stackdriver dependencies.
$ cd stackdriver-core/ $ bundle install
Tests are very important part of stackdriver. All contributions should include tests that ensure the contributed code behaves as expected.
To run the unit tests, documentation tests, and code style checks together for a package:
$ cd stackdriver-core/ $ bundle exec rake ci
To run the command above, plus all acceptance tests, use
rake ci:acceptance or
its handy alias,
Stackdriver Unit Tests
The project uses the minitest library, including specs, mocks and minitest-autotest.
To run the Stackdriver unit tests:
$ cd stackdriver-core/ $ bundle exec rake test
Stackdriver Documentation Tests
The project tests the code examples in the gem's YARD-based documentation.
The example testing functions in a way that is very similar to unit testing, and in fact the library providing it, yard-doctest, is based on the project's unit test library, minitest.
To run the Stackdriver documentation tests:
$ cd stackdriver-core/ $ bundle exec rake doctest
If you add, remove or modify documentation examples when working on a pull
request, you may need to update the setup for the tests. The stubs and mocks
required to run the tests are located in
note that much of the setup is matched by the title of the
If you alter an example's title, you may encounter breaking tests.
Please follow the established coding style in the library. The style is is largely based on The Ruby Style Guide with a few exceptions based on seattle-style:
- Avoid parenthesis when possible, including in method definitions.
- Always use double quotes strings. (Option B)
You can check your code against these rules by running Rubocop like so:
$ cd stackdriver-core/ $ bundle exec rake rubocop
Code of Conduct
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Code of Conduct for more information.