Issue
Contribution records
Contributors

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

Give credit to everyone
hswong3i organization(s): PantaRei Design Limited (Hong Kong)
tr
jsidigital
spudley
lapurddrupal volunteering
gisle organization(s): Hannemyr Nye Medier AS customer(s): Ramsalt Lab
flyke
bserem organization(s): Annertech
superlolo95
xem8vfdh
anybody organization(s): DROWL.de
igonzalez
afagioli volunteering
deg volunteering
arturopanetta
lpsolit volunteering
brunodbo organization(s): Textillia
taran2l organization(s): Lemberg Solutions
j-barnes volunteering
bohus ulrych
rajab natshah organization(s): Vardot customer(s): Vardot
jaime@gingerrobot.com organization(s): Ginger Robot customer(s): Technocrat
oleh chemerys
pallas athena
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.