Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add CLA

...

The first step to contribute to Magnolia is a Jira ticket for the particular contribution (e.g. bug fix, improvement, feature).

Tip

You might also want to consider contacting Magnolia Support as a first step. Support can help with facilitating your contribution into the PD pipeline. They can also help find workarounds.  

(lightbulb) Do search for pre-existing tickets beforehand to avoid duplicates. 

How to create a Pull Request

...

2. Create a development branch on this fork; check out that branch locally.

(lightbulb) You may use the  Conveniently, Jira has a Create branch link from Jirafor that.

3. Commit and push to that branch.

...

If you have an enterprise subscription, advise your technical account manager or support contact at Magnolia, to make sure we assign a Magnolia staff member for review. They will make sure our maintenance team is informed and coordinates the review with Magnolia staff.
If you are a community user, mind that we groom community tickets in Jira once a week. You may still please create a ticket in Jira describing your fix or improvement. Please also drop us a line on the Magnolia Developers Mailing List (wink). Mind that we groom community tickets in Jira once a week.

You will be required to sign the Magnolia Contributor License Agreement.

Once assigned, Magnolia developers will help you as best as possible to discuss the changes, as well as to pass various validation steps (e.g. code style, tests, PR builds).

...