-
Create a branch directly in this repo or a fork (if you don't have push access). Please name branches within this repository
feature/<description>orfix/description. For example, something like `feature/add_httpcode_collector. -
Create an issue or open a pull request (PR). If you aren't sure your PR will solve the issue or may be controversial, we're okay with you opening an issue separately and linking to it in your PR. That way, if the PR is not accepted, the issue will remain and be tracked.
-
Close (and reference) issues by the
closes #XXXorfixes #XXXnotation in the commit message. Please use a descriptive, useful commit message that could be used to understand why a particular change was made. Keep pushing commits to the initial branch using--amend/--rebaseas necessary, and don't mix unrelated issues in a single branch. -
Clean up the branch (rebase with master to synchronize, squash, edit commits, etc.) to prepare for it to be merged.
- After reviewing commits for descriptive commit messages, documentation, passed continuous integration (CI) tests, version bumps, and a changelog, a project maintainer can merge.
- Create/update the changelog if necessary.