Thank you for your interest in contributing to Okta's Open Source Projects! Before submitting a PR, please take a moment to read over our Contributer License Agreement. In certain cases, we ask that you sign a CLA before we merge your pull request.
We use an adapted form of Conventional Commits.
- Use the present tense ("Adds feature" not "Added feature")
- Limit the first line to 72 characters or less
- Add one feature per commit. If you have multiple features, have multiple commits.
<type>: Short Description of Commit
<BLANKLINE>
More detailed description of commit
<BLANKLINE>
(Optional) Resolves: <Issue #>
<type>[<package-name>]: Short Description of Commit
<BLANKLINE>
More detailed description of commit
<BLANKLINE>
(Optional) Resolves: <Issue #>
Our types include:
feat
when creating a new featurefix
when fixing a bugtest
when adding testsrefactor
when improving the format/structure of the codedocs
when writing docsrelease
when pushing a new releasechore
others (ex: upgrading/downgrading dependencies)
docs: Updates CONTRIBUTING.md
Updates Contributing.md with new emoji categories
Updates Contributing.md with new template
Resolves: #1234
fix[okta-angular]: Fixes bad bug
Fixes a very bad bug in okta-angular
Resolves: #5678
- Breaking changes MUST be indicated at the very beginning of the body section of a commit. A breaking change MUST consist of the uppercase text
BREAKING CHANGE
, followed by a colon and a space. - A description MUST be provided after the
BREAKING CHANGE:
, describing what has changed about the API.
feat: Allows provided config object to extend other configs
BREAKING CHANGE: `extends` key in config file is now used for extending other config files