Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
ToxaViking
yanniboi organization(s): FreelyGive
bisonbleu
klausi
fago organization(s): drunomics
jaypan organization(s): Jaypan
ckaotik organization(s): werk21
akcakaya
anas_maw volunteering
pyxio
rodmarasi
tr
chrisolof organization(s): Lima Solutions customer(s): CivicSolar, Inc.
aiphes
webdevfreak organization(s): BWS LONDON
wombatbuddy
Sandoran
rivimey volunteering organization(s): IvimeyCom
jonathan1055 volunteering
paul_serval
ronaldmulero organization(s): U.Group
nicasso
rrotari organization(s): Hogarth Worldwide
joelrotelli
ttnt
alison volunteering
sl27257 volunteering
stevenx
laarrrx
saranya ashokkumar organization(s): UniMity Solutions Pvt Limited
max-kuzomko volunteering
alex.skrypnyk organization(s): DrevOps
kevin w organization(s): City of Portland
martijn houtman
thomas.wardin
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.