This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 223
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e62910a
commit 65b1e17
Showing
3 changed files
with
50 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,45 @@ | ||
# Contributing to TimescaleDB Kubernetes | ||
# Contributing to Timescale Helm Charts | ||
|
||
We appreciate any help the community can provide to make TimescaleDB better! | ||
We'd love your help! | ||
|
||
You can help in different ways: | ||
## How to Contribute | ||
|
||
* Open an [issue](https://github.com/timescale/timescaledb-kubernetes/issues) with a | ||
bug report, build issue, feature request, suggestion, etc. | ||
1. Fork this repository | ||
1. Develop, and test your changes | ||
1. Submit a pull request | ||
|
||
* Fork this repository and submit a pull request | ||
_NOTE_: In order to make testing and merging of PRs easier, please submit changes to multiple charts in separate PRs. | ||
|
||
For any particular improvement you want to make, it can be beneficial to | ||
begin discussion on the GitHub issues page. This is the best place to | ||
discuss your proposed improvement (and its implementation) with the core | ||
development team. | ||
Remember to always work in a branch of your local copy, as you might otherwise | ||
have to contend with conflicts in master. | ||
|
||
Before we accept any code contributions, Timescale contributors need to | ||
sign the [Contributor License Agreement](https://cla-assistant.io/timescale/timescaledb-kubernetes) (CLA). By signing a CLA, we can | ||
ensure that the community is free and confident in its ability to use your | ||
contributions. | ||
Please also see [GitHub | ||
flow](https://docs.github.com/en/get-started/quickstart/github-flow). | ||
|
||
### Technical Requirements | ||
|
||
* Must pass [CLA check](https://cla-assistant.io/timescale/helm-charts) | ||
* Must follow [Charts best practices](https://helm.sh/docs/topics/chart_best_practices/) | ||
* Must pass CI jobs for linting and installing changed charts with the | ||
[chart-testing](https://github.com/helm/chart-testing) tool | ||
* Any change to a chart requires a version bump following | ||
[semver](https://semver.org/) principles. See [Immutability](#immutability) | ||
and [Versioning](#versioning) below | ||
|
||
Once changes have been merged, the release job will automatically run to package | ||
and release changed charts. | ||
|
||
### Immutability | ||
|
||
Chart releases must be immutable. Any change to a chart warrants a chart version | ||
bump even if it is only changed to the documentation. | ||
|
||
### Versioning | ||
|
||
The chart `version` should follow [semver](https://semver.org/). | ||
|
||
Charts should start at `0.1.0` or `1.0.0`. Any breaking (backwards incompatible) | ||
changes to a chart should: | ||
|
||
1. Bump the MAJOR version | ||
2. In the README or appropriate document, describe the manual steps necessary to upgrade to the new (specified) MAJOR version |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters