Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Make it clear that we prefer pull requests over patches

...

Then we can add your issue to Git and then we'll know when its really fixed and
we can ensure that the problem stays fixed in future releases.

Submitting Github pull requests

The preferred way of contributing code to Groovy is by submitting a Pull Request to the project on Github.

The best workflow for this is to raise a new issue in the tracker (see below), fix the code in a branch on your forked project, and submit a pull request via the Github UI (mentioning the Jira Issue ID in the pull request, and then commenting the Jira ticket with the ID of the pull request so that both can be tied together).

One workflow you could use is described in a blog post here.

Submitting patches

We gladly accept patches if you can find ways to improve, tune or fix Groovy in some way.

Most IDEs can create nice patches now very easily. If you're a command line person try the following to create the patch

...

Once you've created a patch the best way to submit it is to raise a new issue in the issue tracker (see below) and maybe send us a mail on the developer list letting us know about the patch.

Submitting Github Pull Requests

Another way of contributing code to Groovy is by submitting a Pull Request to the project on Github.

The best workflow for this is to raise a new issue in the tracker (see below), fix the code in a branch on your forked project, and submit a pull request via the Github UI (mentioning the Jira Issue ID in the pull request, and then commenting the Jira ticket with the ID of the pull request so that both can be tied together).

One workflow you could use is described in a blog post here.

Using the issue tracker

Before you can raise an issue in the issue tracker you need to register with it. This is quick & painless.

...