Issue
Contribution records
Contributors

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

Give credit to everyone
gapple volunteering organization(s): Myplanet
joelpittet organization(s): The University of British Columbia
mohit1604 organization(s): Google Summer of Code
zymbian volunteering
catch organization(s): Third and Grove
pifagor organization(s): GOLEMS GABB customer(s): GOLEMS GABB
alexpott volunteering
MerryHamster organization(s): Skilld
andypost volunteering organization(s): Skilld
ksbuble
yogeshmpawar volunteering organization(s): QED42
vsujeetkumar organization(s): Material customer(s): Drupal India Association
mradcliffe organization(s): Kosada
bakulahluwalia
berdir organization(s): MD Systems GmbH
amjad1233 volunteering
philipnorton42 volunteering organization(s): Code Enigma
jplana
rachel_norfolk organization(s): Drupal Association
nlisgo
smustgrave organization(s): Mobomo
smokris organization(s): Kosada customer(s): Kosada
larowlan volunteering organization(s): PreviousNext
a.milkovsky organization(s): Styria Digital Services
suresh prabhu parkala organization(s): Specbee
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.