-
-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #123 from KenshiTech/feature/cz
Feature/cz
- Loading branch information
Showing
20 changed files
with
165 additions
and
34 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
--- | ||
commitizen: | ||
major_version_zero: true | ||
name: cz_gitmoji | ||
tag_format: v$version | ||
update_changelog_on_bump: true | ||
version: 0.11.21 | ||
version_scheme: semver |
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 |
---|---|---|
|
@@ -19,4 +19,4 @@ docker/pgadmin | |
node_trace.* | ||
internal/bin | ||
conf.*.private | ||
.idea | ||
.idea |
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 |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# See https://pre-commit.com for more information | ||
# See https://pre-commit.com/hooks.html for more hooks | ||
repos: | ||
- repo: https://github.com/pre-commit/pre-commit-hooks | ||
rev: v4.6.0 | ||
hooks: | ||
- id: trailing-whitespace | ||
- id: end-of-file-fixer | ||
- id: check-json | ||
- id: check-added-large-files | ||
- id: check-shebang-scripts-are-executable | ||
- id: detect-private-key | ||
- id: forbid-submodules | ||
- id: mixed-line-ending | ||
|
||
- repo: https://github.com/TekWizely/pre-commit-golang | ||
rev: v1.0.0-rc.1 | ||
hooks: | ||
- id: go-fmt | ||
- id: go-mod-tidy | ||
- id: go-imports | ||
- id: golangci-lint-repo-mod | ||
|
||
- repo: https://github.com/adrienverge/yamllint | ||
rev: v1.35.1 | ||
hooks: | ||
- id: yamllint | ||
|
||
- repo: https://github.com/commitizen-tools/commitizen | ||
rev: v3.21.3 | ||
hooks: | ||
- id: commitizen | ||
additional_dependencies: | ||
- "cz-conventional-gitmoji" | ||
- id: commitizen-branch | ||
additional_dependencies: | ||
- "cz-conventional-gitmoji" | ||
stages: [push] | ||
|
||
- repo: https://github.com/ljnsn/cz-conventional-gitmoji | ||
rev: v0.2.4 | ||
hooks: | ||
- id: conventional-gitmoji |
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 |
---|---|---|
@@ -0,0 +1,18 @@ | ||
extends: relaxed | ||
|
||
yaml-files: | ||
- '*.yaml' | ||
- '*.yaml.template' | ||
- '*.yml' | ||
- '.yamllint' | ||
|
||
ignore: | ||
- k8s/charts/unchained-worker/* | ||
- '*.private/*' | ||
- '*.private.yaml' | ||
|
||
rules: | ||
indentation: | ||
spaces: 2 | ||
|
||
line-length: disable |
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,52 +1,86 @@ | ||
# Contributing to Unchained | ||
|
||
Thank you for your interest in contributing to Unchained! We value your contributions and want to make sure the process is easy and beneficial for everyone involved. Please take a moment to read these guidelines to ensure a smooth contribution process. | ||
Thank you for your interest in contributing to Unchained! We value your | ||
contributions and want to make sure the process is easy and beneficial for | ||
everyone involved. Please take a moment to read these guidelines to ensure a | ||
smooth contribution process. | ||
|
||
## Contribution Guidelines | ||
|
||
### 1. Contributor License Agreement (CLA) | ||
|
||
Before your contributions can be accepted, you must sign a Contributor License Agreement (CLA). This is a simple process that happens when you make your first pull request (PR). | ||
Before your contributions can be accepted, you must sign a Contributor License | ||
Agreement (CLA). This is a simple process that happens when you make your first | ||
pull request (PR). | ||
|
||
### 2. Forking and Branching Strategy | ||
|
||
- **External Contributors**: Please fork the repository and submit your changes via a pull request from your fork. | ||
- **Internal Contributors**: You should push your branches directly to the main project repository. | ||
- **External Contributors**: Please fork the repository and submit your changes | ||
via a pull request from your fork. | ||
- **Internal Contributors**: You should push your branches directly to the main | ||
project repository. | ||
|
||
### 3. Issues and Pull Requests | ||
|
||
- **Creating Issues**: Always create a GitHub issue before starting work on a pull request. Search for existing issues to avoid duplicates and check if someone else is already working on it. | ||
- **Naming Branches**: Use semantic and meaningful branch names to make it clear what your contribution entails. Here are some good and bad examples: | ||
- **Creating Issues**: Always create a GitHub issue before starting work on a | ||
pull request. Search for existing issues to avoid duplicates and check if | ||
someone else is already working on it. | ||
- **Naming Branches**: Use semantic and meaningful branch names to make it clear | ||
what your contribution entails. Here are some good and bad examples: | ||
|
||
**Good Examples** | ||
|
||
- `add-{x}-to-{y}-{issue-number}` | ||
- `fix-{x}-in-{y}-{issue-number}` | ||
- `feature-{xyz}-{issue-number}` | ||
- `test-{xyz}-{issue-number}` | ||
|
||
**Bad Examples** | ||
|
||
- `bugfix` | ||
- `potatoes` | ||
- `mybranch` | ||
- `johns-first-pr` | ||
|
||
### 4. Coding Standards | ||
|
||
- **Documentation**: Your code must be well-documented and commented. Aim for clarity and simplicity; your code should be easily understandable without relying solely on comments. | ||
- **Naming Conventions**: Use descriptive and appropriate names for variables, functions, and branches to clearly convey their purpose. | ||
- **Pull Request Details**: Ensure your pull requests and issues clearly describe what you're trying to achieve. This helps reviewers understand your intentions and the impact of your contributions. | ||
- **Documentation**: Your code must be well-documented and commented. Aim for | ||
clarity and simplicity; your code should be easily understandable without | ||
relying solely on comments. | ||
- **Naming Conventions**: Use descriptive and appropriate names for variables, | ||
functions, and branches to clearly convey their purpose. | ||
- **Pull Request Details**: Ensure your pull requests and issues clearly | ||
describe what you're trying to achieve. This helps reviewers understand your | ||
intentions and the impact of your contributions. | ||
|
||
### 5. Pull Request Process | ||
|
||
- Your PR should always target the `develop` branch. | ||
- If the `develop` branch is updated before your PR is merged, you must rebase your commits to keep the history clean and avoid merge conflicts. | ||
- If the `develop` branch is updated before your PR is merged, you must rebase | ||
your commits to keep the history clean and avoid merge conflicts. | ||
|
||
### 6. Commit Messages and Pull Requests | ||
|
||
We use commitizen for commit and changelog management. You'll need the following | ||
tools to get started: | ||
|
||
- [Pre-commit](https://pre-commit.com/): Used for various pre-commit checks | ||
including commit message lint checks. | ||
- [Commitizen](https://commitizen-tools.github.io): Used for creating commit | ||
messages and maintaining a logfile. | ||
- [Golangci-lint](https://golangci-lint.run/): Used for Golang lint checks. | ||
|
||
### 6. Commit Messages | ||
You'll need to run the following command to setup the pre-commit hooks: | ||
|
||
Commit messages should be descriptive and meaningful, helping to explain why and what you have done without needing to look at the source code directly. Please avoid using emojis and stick to ASCII readable characters to ensure clarity and compatibility. | ||
```sh | ||
pre-commit install --install-hooks --hook-type commit-msg --hook-type pre-push | ||
``` | ||
|
||
## Conclusion | ||
|
||
Following these guidelines helps us maintain a high standard of quality for our project and makes the contribution process more efficient and effective. We look forward to your contributions and are excited to see what we can achieve together in Unchained! | ||
Following these guidelines helps us maintain a high standard of quality for our | ||
project and makes the contribution process more efficient and effective. We look | ||
forward to your contributions and are excited to see what we can achieve | ||
together in Unchained! | ||
|
||
Thank you for contributing! |
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
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 |
---|---|---|
|
@@ -40,4 +40,3 @@ imports: | |
|
||
fmt: | ||
go fmt ./... | ||
|
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
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
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
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 |
---|---|---|
|
@@ -86,7 +86,7 @@ spec: | |
- metadata: | ||
name: data | ||
spec: | ||
accessModes: | ||
accessModes: | ||
- ReadWriteOnce | ||
resources: | ||
requests: | ||
|
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
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