Issue
Contribution records
Contributors

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

Give credit to everyone
roysegall organization(s): Gizra
amitaibu
amateescu customer(s): Pfizer, Inc.
dpi organization(s): PreviousNext
jibran organization(s): PreviousNext customer(s): Service NSW
berdir organization(s): MD Systems GmbH
mpolishchuck organization(s): Alpha Web Group customer(s): Dazzle
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
gpap
johnnydarkko organization(s): Sage Tree Solutions
colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
brooke_heaton
mrinalini9 organization(s): Material customer(s): Drupal India Association
hchonov organization(s): 1xINTERNET
rwohleb
ranjith_kumar_k_u organization(s): Zyxware Technologies
sourabhjain organization(s): Valuebound customer(s): Valuebound
quietone organization(s): PreviousNext
rpayanm
zarpele organization(s): Ocelot customer(s): Ocelot
bnjmnm organization(s): Acquia
vasike organization(s): JAKALA (formerly FFW) customer(s): JAKALA (formerly FFW)
smustgrave organization(s): Mobomo
flocondetoile organization(s): Flocon de toile
larowlan organization(s): PreviousNext
acbramley organization(s): PreviousNext customer(s): University of Adelaide
martijn de wit organization(s): Ablerz
dhirendra.mishra organization(s): Material
raman.b organization(s): OpenSense Labs
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.