Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
trobey volunteering
cilefen
jerenus volunteering
boobaa organization(s): Pronovix customer(s): Brightcove
fernly organization(s): Dropsolid customer(s): District09
catch organization(s): Third and Grove
pandaski organization(s): govCMS (Australian Government Department of Finance)
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
alexpott organization(s): Acro Commerce, Thunder
junaidpv organization(s): Detlus customer(s): Wickwood Marketing
miro_dietiker organization(s): MD Systems GmbH
longwave organization(s): Full Fat Things
dww volunteering
larowlan organization(s): PreviousNext
robin.ingelbrecht organization(s): EntityOne
mr.baileys organization(s): SQLI - Belgium
george.karaivanov organization(s): Peytz - part of iO
ravi.shankar organization(s): OpenSense Labs
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.