Contribution records
Draft
Contributors

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

Give credit to everyone
bojanz bojanz
atlea atlea
rszrama rszrama
emptyvoid emptyvoid
googletorp googletorp
helior heliorcolorado
arun_ms arun_ms
andyg5000 andyg5000
cvangysel stophr
Zac_JH roodoo
joshmiller joshmiller
brephraim brephraim
franz franz
illmatix illmatix
delta delta
Daemon_Byte Daemon_Byte
mglaman mglaman
jessepinho jessepinho
primozsusa primozsusa
IckZ IckZ
mibfire mibfire
luksak luksak
bgilhome bgilhome
joelpittet joelpittet
xurizaemon xurizaemon
mstrelan mstrelan
torgospizza torgospizza volunteering
siva_drupal siva_drupal volunteering
arunkumark arunkumark volunteering organization(s): DrupalPartners customer(s): BinaryWorks
rokurtz rokurtz
Kris D. Kris_D
dave bruns dave_bruns
rob c robc
office@w3k.at LuckySoul
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.