eZ Publish is a fully open source and community-driven project. Code contributions are simply done via github Pull Requests.
Contribute
Workflow
- Remember to first create a issue in our issue tracker and refer to it in commits and Pull Requests headers.
- Examples:
- "Implement EZP-201xx: Add support for X in Y"
- "Fix EZP-20104: ContentController should return error status when content is not found"
- Keep different changes in different commits in case cherry-pick is preferred instead of a merge later.
- A Pull Request should only cover one issue.
- A commit should not contain code changes at the same time as doing coding standards/whitespace/typo fixes.
If you want to contribute implementation specification proposals, place them in doc/ folder.
Testing
- TDD: Write/Change the test(s) for the change you do and commit it before you do the actual code change
- If a bug affects Public API, write or enhance a integration test to make sure the bug is covered.
- Unit tests should only use mocks/stubs and never test the full stack like integrations tests does.
- Please test/check your commits before pushing:
- Run unit tests and integration test before commits
Make sure you follow our coding standards
See also
For further information please have a look at the related guidance page.
Learn
You will, amongst other, learn how to make pull-requests. More on this here : "How to contribute to eZ Publish using GIT".
Add Comment