Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
marcingy
brenk28
jenlampton organization(s): Jeneration Web Development
scottalan
cweagans
giorgosk
sun
mitron
paulmicha
yoroy
dpolant
capellic
manningpete
jelle_s organization(s): Attiks
klidifia
akosipax
amklose
colan organization(s): Colan Schwartz Consulting
mikeker volunteering
bartk
grienauer organization(s): acolono GmbH
slanger
gnuget volunteering organization(s): Agaric
hongpong volunteering organization(s): kor group
matsbla
bartnelissen
jumoke
izus
wells organization(s): Cascade PBS
gordon organization(s): Heydon Consulting
jjancel volunteering
finex volunteering
rgpublic
rodrigoaguilera volunteering
gintass
bbu23 organization(s): Ninja Coders
tonytheferg
smustgrave organization(s): Mobomo
alecsmrekar volunteering
raphael apard
kevin morse
David Hernández
jan.ptacek
joseph.olstad
narendra.rajwar27 volunteering organization(s): Material customer(s): Drupal India Association
dcam
grimreaper volunteering
Git commit message
Commit types
  • 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

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.