Skip to content

Latest commit

 

History

History
55 lines (39 loc) · 3.21 KB

CONTRIBUTING.md

File metadata and controls

55 lines (39 loc) · 3.21 KB

Contributor License

If this is your first time contributing to an Eclipse Foundation project, you'll need to sign the Eclipse Contributor Agreement.

Issues

Search the issue tracker for a relevant issue or create a new one. Comment on the issue expressing your interest to work on it. One of the project maintainers will assign the issue to you.

Making changes

  • Fork the repository in GitHub and make changes in your fork.
  • Submit a pull request.

Details on working with GitHub for Eclipse Collections is located at the Eclipse Collections Wiki.

Contact us

Join the mailing list and email the community at [email protected] to discuss your ideas and get help.

Coding Style

Eclipse Collections Kata follows a coding style that is similar to Google's Style Guide for Java, but with curly braces on their own lines.

Avoid changing whitespace on lines that are unrelated to your pull request. This helps preserve the accuracy of the git blame view, and makes code reviews easier.

Commit messages

Pull requests

Excessive branching and merging can make git history confusing. With that in mind

Submit your pull request when ready. Three checks will be kicked off automatically.

  • IP Validation: Checks that all committers signed the Eclipse CLA and signed their commits.
  • Continuous integration: GitHub Actions that run JUnit tests.
  • The standard GitHub check that the pull request has no conflicts with the base branch.

Make sure all the checks pass. One of the committers will take a look and provide feedback or merge your contribution.

That's it! Thanks for contributing to the Eclipse Collections Kata!