CONTRIBUTING.md

How to Contribute

We're excited you're interested in contributing to Marquez! We'd love your help, and there are plenty of ways to contribute:

• Fix or report a bug
• Fix or improve documentation
• Pick up a "good first issue", then send a pull request our way

We feel that a welcoming community is important and we ask that you follow the Contributor Covenant Code of Conduct in all interactions with the community.

Development

To run the entire test suite:

$ ./gradlew test

You can also run individual tests using the flag --tests:

$ ./gradlew test --tests marquez.client.MarquezClientTest
$ ./gradlew test --tests marquez.client.models.DatasetMetaTest

Or run tests by category:

$ ./gradlew testUnit  # run only unit tests

We use spotless to format our code. This ensures .java files are formatted to comply with Google Java Style. Make sure your code is formatted before pushing any changes, otherwise CI will fail:

$ ./gradlew spotlessApply

Note: To make formatting code simple, we recommend installing a plugin for your favorite IDE. We also us Lombok. Though not required, you might want to install the plugin as well.

Publish to Local Maven Repository

Use publishToMavenLocal to publish artifacts to your local maven repository:

$ ./gradlew publishToMavenLocal

Submitting a Pull Request

1. Fork and clone the repository
2. Make sure all tests pass locally: ./gradlew test
3. Create a new branch: git checkout -b feature/my-cool-new-feature
4. Make change on your cool new branch
5. Write a test for your change
6. Make sure .java files are formatted: ./gradlew spotlessJavaCheck
7. Run code lint checks: ./gradlew check
8. Make sure to sign you work
9. Push change to your fork and submit a pull request
10. Work with project maintainers to get your change reviewed and merged into the master branch
11. Delete your branch

To ensure your pull request is accepted, follow these guidelines:

• All changes should be accompanied by tests
• Do your best to have a well-formed commit message for your change
• Keep diffs small and self-contained
• If your change fixes a bug, please link the issue in your pull request description

Note: A pull request should generally contain only one commit (use git commit --amend and git push --force or squash existing commits into one).

Branching

• Use a group at the beginning of your branch names

  wip      Work on a feature is still in progress
  feature  Add or expand a feature
  bug      Fix a bug
  

  For example:

  wip/my-cool-new-wip-feature
  feature/my-cool-new-feature
  feature/my-other-cool-new-feature
  bug/my-bug-fix
  bug/my-other-bug-fix
  

• Choose short and descriptive branch names

• Use dashes (-) to separate words in branch names

• Use lowercase in branch names

Sign Your Work

The sign-off is a simple line at the end of the message for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material (see Developer Certificate of Origin):

This is my commit message

Signed-off-by: Remedios Moscote <remedios.moscote@buendía.com>

Git has a -s command line option to append this automatically to your commit message:

$ git commit -s -m "This is my commit message"

Resources

• How to Contribute to Open Source
• Using the Fork-and-Branch Git Workflow
• Keep a Changelog
• Code Review Developer Guide