Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
awolfey organization(s): Capellic LLC
seanb
borisson_ organization(s): Calibrate
anas_maw volunteering
alexpott organization(s): Acro Commerce, Thunder
catch organization(s): Third and Grove
charly71
idebr organization(s): iO
om_kha volunteering
mradcliffe organization(s): Kosada
pol volunteering
rob_pr
aaronpinero volunteering
renrhaf organization(s): CGI customer(s): Ville de Montréal
jberube
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
cbanman organization(s): Acro Commerce
ao5357 volunteering organization(s): Solve it once
jeetmail72
tlo405
nicholass
smustgrave organization(s): Mobomo
greggles organization(s): Morris Animal Foundation
codebymikey organization(s): Zodiac Media
jelle_s
nigelcunningham
wilfred.waltman volunteering
darren oh volunteering organization(s): Cognizant Softvision
rithesh bk volunteering organization(s): Valuebound customer(s): Valuebound
Ankit.Gupta organization(s): Dotsquares Ltd.
shubham chandra volunteering organization(s): Dotsquares Ltd.
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.