Contributing to Valtimo
Last updated
Last updated
Create an issue in the or issues repository.
Tag the Product Owner in the Github issue. A member of the product team will be in touch to discuss the issue and the proposed solution.
The Github handle of the Product Owner can be found in the README.md of the issue repositories.
Implement the feature/bugfix in the library repository/repositories and . No reviewers are necessary.
Instructions on how to run Valtimo locally can be found in the README.md of the library repositories.
Write release notes and documentation for the feature. See below for instructions on how to do this.
Merge the PR after getting an approval from the Valtimo team.
There are two different circumstances for which documentation for Valtimo can be written. Either because it is related to a particular change in the product that will be included in an upcoming release, or to add something to the documentation that is not related to an upcoming release (e.g. fixing spelling errors, or documenting part of an already existing feature).
The source of the Valtimo documentation is .
Information on what language to use, as well as general guidelines can be found .
If new pages are added, these should also be added to SUMMARY.md
. The sidebar shown on the Valtimo documentation corresponds to this structure.
Write documentation/release notes and .
Use the same base- and target branch as the changes in the library:
next-minor
for non-breaking changes
next-major
for breaking changes.
Merge the PR after getting an approval from the Valtimo team.
In case of a new page, discuss the documentation you want to write with someone from the Valtimo team.
Use next-minor
as base- and target branch.
Merge the PR after getting an approval from the Valtimo team.
Write documentation and .
For both changes to the library and the documentation, it is required to fork the repository to implement the changes and create the PR. More information can be found .