How to Contribute
When contributing to this repository, please first discuss the change you wish to make via submitting an issue with the owners of this repository before making a change. Fixing typos or rephrasing for better understanding DO NOT require discussion.
This repository holds two main branches with an infinite lifetime:
masteris the default branch which always reflects the latest release.
developis the main branch reflecting the latest delivered changes for the next release. When the
developbranch reaches a stable point and is ready to be released, then all changes should be merged back into
A variety of supporting branches are used to aid parallel development. These branches have a limited lifespan, since they will be removed eventually.
Contributions to this repository are welcome. For ease of managing, please follow the steps below:
Fork this repository to your account.
Clone your copy of this repository, locally.
git clone https://github.com/YOU/API-Security.git
Create a new branch based on
git checkout develop && git checkout -b fix/foreword-section
Apply your changes.
Please, always follow our style conventions.
Although there's an
.editorconfigfile on repository's root, your editor may not support it. To learn more about EditorConfig and text editors/IDEs support, check the website: https://editorconfig.org/.
Commit your changes.
- Check modified files and add only required ones (e.g., build artifacts SHOULD NOT be tracked).
- The first line of the commit message should provide a brief description of your changes. You can go into more details on the optional commit message body.
Push changes to your public repository.
git push origin fix/foreword-section
Open a Pull Request from your
fix/foreword-sectionto the upstream repository