Issue
Contribution records
Contributors

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

Give credit to everyone
stevector
dhina
13rac1
merlinofchaos
damienmckenna organization(s): Current
danielnolde
xen organization(s): Reload
acbramley
xtfer
frakke
grndlvl
alexkb
tobby
recidive
warpedgeoid
jedihe
sylus
russ86
jojonaloha
grasmash organization(s): Acquia customer(s): U.S. Department of Justice
hernani
saltednut
skek
colan
geerlingguy
asgorobets
joelpittet
alcroito
seanpclark
eclipsegc organization(s): Acquia
gremy
thtas
chrisgross
bcyde
whthat
brockfanning
dbyers55
davewilly volunteering
drumm organization(s): Drupal Association
mile23 volunteering
jlapp
loopduplicate
rob_johnston
fullerja
Jean Gionet
Bram Tassyns
eugene.ilyin
joseph.olstad
ben buske organization(s): werk21
japerry organization(s): Acquia
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.