Contributor License

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

Create an account on dev.eclipse.org
Open your Account Settings tab, enter your GitHub ID and click Update Account
Read and sign the CLA
Your git commits must be signed off
Use the exact same email address for your Eclipse account, your commit author, and your commit sign-off.

Making changes

Fork the repository in GitHub, make changes in your fork and submit a pull request.

The gsc-ec-converter follows a coding style that is similar to Google's Style Guide for Java, but with curly braces on their own lines.

Use the imperative mood as in "Fix bug" or "Add feature" rather than "Fixed bug" or "Added feature"
[Mention the GitHub issue][github-issue] when relevant
It's a good idea to follow the advice in Pro Git
Sign-off your commits using git commit --signoff or git commit -s for short

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

Squash your commits down to a few commits, or one commit, before submitting a pull request
Rebase your pull request changes on top of the current master. Pull requests shouldn't include merge commits.

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

IP Validation: Checks that all committers signed the Eclipse CLA and signed their commits.
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 gsc-ec-converter!