Skip to content

Latest commit

 

History

History
30 lines (19 loc) · 1.79 KB

contribute.md

File metadata and controls

30 lines (19 loc) · 1.79 KB

Contribute

[Up] [Top]

Table of Content

  1. How to Contribute Features and Fixes
  2. Branches and Tags

How to Contribute Features and Fixes

As an external developer, we want to encourage you contributing to this extension, so that others can benefit from your fixes and features too. Contributing is as easy as:

  1. Create an issue for your feature in the original repository on GitHub.
  2. Fork the repository and implement your change.
  3. Send us a Pull Request as described here targeted at the develop branch.

Developers at CoreMedia don't necessarily need a fork of the repository. They have the required rights to create Pull Requests on the original repository.

⑃ Branches and Tags

This is of course only one approach on how you can manage branches in your project. Depending on your release cycle and development approach, there are of course other branch patterns that are better suited for your project. This branch model is our best practice if you want to deploy your extension by means of the CoreMedia CI.

  • main: Will be initially used to create develop branch. Afterwards, it will just be used to merge changes from develop branch to main, i.e., it will just be recipient afterwards. On release the main merge commit will be tagged. See below for details on tagging.
  • develop: After initial creation, all development by CoreMedia and merging pull requests will happen here.