File: CONTRIBUTING.md

package info (click to toggle)
sonivox 4.0.1-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 26,676 kB
  • sloc: ansic: 77,919; python: 8,597; cpp: 356; asm: 281; xml: 28; makefile: 5
file content (26 lines) | stat: -rw-r--r-- 1,188 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
# Contributing to Sonivox

Thank you for considering contributing to Sonivox!

## Workflow

We do not allow merge requests into the `master` branch directly. Please follow these steps:

1. Fork (and clone) the repository. If you already had a fork from previous contributions, then [sync your fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) from time to time.
2. Create a new branch from `devel` for your changes.
3. Open an issue describing the contributions you plan to make.
4. Make your changes and commit them with clear commit messages.
5. Open a pull request to merge your changes into the `devel` branch.

## Coding Standards

- Follow the existing coding style.
- Write clear and concise commit messages.
- Ensure your code passes all tests.

## Pull Requests

When opening a pull request, please:
- Describe the changes you've made.
- [Link to the issue](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue) describing your contributions.
- Ensure your code follows the contribution guidelines.