Contribution records
Contributors

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

Give credit to everyone
mooffie mooffie
quicksketch quicksketch
gausarts gausarts
aaron aaron
Apollo610 Apollo610
johnnytyranno johnnytyranno
robertdjung robertdjung
RoboPhred robophred
tobiberlin tobiberlin
manop manop
gunzip gunzip
netentropy netentropy
minus minus
aharown07 aharown07
RicardoJBarrios RicardoJBarrios
ordually ordually
jontyler jontyler
dhalgren dhalgren
highvoltage highvoltage
xn2001 xn2001
milham milham
inuninu inuninu
lameei lameei
pribeh pribeh
Flying Drupalist Flying_Drupalist
dave reid davereid
Mtt-2 Mtt-2
greg.harvey greg.harvey
henrijs.seso mansspams
Gabriel R. GR
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.