|
| 1 | +# Contributing |
| 2 | + |
| 3 | +## Submission guidelines |
| 4 | + |
| 5 | +### Report a bug |
| 6 | + |
| 7 | +Before creating an issue please make sure you have checked out the docs, you might want to also try searching Github. It's pretty likely someone has already asked a similar question. |
| 8 | + |
| 9 | +Issues can be reported in the [issue tracker](https://github.com/kalisio/k-awc/issues). |
| 10 | + |
| 11 | +### Pull Requests |
| 12 | + |
| 13 | +We love pull requests and we're continually working to make it as easy as possible for people to contribute. |
| 14 | + |
| 15 | +We prefer small pull requests with minimal code changes. The smaller they are the easier they are to review and merge. A core team member will pick up your PR and review it as soon as they can. They may ask for changes or reject your pull request. This is not a reflection of you as an engineer or a person. Please accept feedback graciously as we will also try to be sensitive when providing it. |
| 16 | + |
| 17 | +Although we generally accept many PRs they can be rejected for many reasons. We will be as transparent as possible but it may simply be that you do not have the same context or information regarding the roadmap that the core team members have. We value the time you take to put together any contributions so we pledge to always be respectful of that time and will try to be as open as possible so that you don't waste it. |
| 18 | + |
| 19 | +## Commit message guidelines |
| 20 | + |
| 21 | +We follow the [Conventional commits specifications](https://www.conventionalcommits.org/en/v1.0.0-beta.3/) which provides a set of rules to make commit messages more readable when looking through the project history. But also, we use the git commit messages to generate the change log. |
| 22 | + |
| 23 | +### Commit message format |
| 24 | + |
| 25 | +The commit message should be structured as follows: |
| 26 | + |
| 27 | +``` |
| 28 | +<type>: <subject> [optional `breaking`] |
| 29 | +``` |
| 30 | + |
| 31 | +Where `type` must be one of the following: |
| 32 | +* `build`: changes that affect the build system (external dependencies) |
| 33 | +* `ci`: changes to our CI configuration files and scripts |
| 34 | +* `chore`: changes that affect the project structure |
| 35 | +* `docs`: changes that affect the documentation only |
| 36 | +* `feat`: a new feature |
| 37 | +* `fix`: a bug fix |
| 38 | +* `perf`: a code change that improves performance |
| 39 | +* `refactor`: a code change that neither fixes a bug nor adds a feature |
| 40 | +* `revert`: revert changes |
| 41 | +* `style`: changes that do not affect the meaning of the code (lint issues) |
| 42 | +* `test`: adding missing tests or correcting existing tests |
| 43 | + |
| 44 | +Use the optional `[ breaking ]` keyword to declare a **BREAKING CHANGE**. |
| 45 | + |
| 46 | +### Examples |
| 47 | + |
| 48 | +* Commit message with description and breaking change in body |
| 49 | +``` |
| 50 | +feat: allow provided config object to extend other configs [ breaking ] |
| 51 | +``` |
| 52 | + |
| 53 | +* Commit message with no body |
| 54 | +``` |
| 55 | +docs: correct spelling in the contributing.md file |
| 56 | +``` |
| 57 | + |
| 58 | +* Commit message for a fix using an issue number. |
| 59 | +``` |
| 60 | +fix: fix minor issue in code (#12) |
| 61 | +``` |
| 62 | + |
| 63 | +## Versioning guidelines |
| 64 | + |
| 65 | +We rely on [Semantic Versioning](https://semver.org/) for versioning a release. Indeed, given a version number `MAJOR.MINOR.PATCH`, increment the: |
| 66 | +* `MAJOR` version when you make a major evolution leading to breaking changes, |
| 67 | +* `MINOR` version when you add functionality in a backwards-compatible manner |
| 68 | +* `PATCH` version when you make backwards-compatible bug fixes. |
| 69 | + |
| 70 | +The command `npm run release:<type>`, where `<type>` is either `patch`, `minor` or `major`, helps you to do the release. |
| 71 | + |
| 72 | +It performs the following task for you: |
| 73 | +* increase the package version number in the `package.json` file |
| 74 | +* generate the change log |
| 75 | +* create a tag accordingly in the git repository and push it |
| 76 | + |
| 77 | +## Contributor Code of Conduct |
| 78 | + |
| 79 | +As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. |
| 80 | + |
| 81 | +We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion. |
| 82 | + |
| 83 | +Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. |
| 84 | + |
| 85 | +Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. Project maintainers who do not follow the Code of Conduct may be removed from the project team. |
| 86 | + |
| 87 | +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers. |
| 88 | + |
| 89 | +This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.0.0, available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/) |
0 commit comments