Contribution records
Contributors

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

Give credit to everyone
stijnbe stijnbe
kompis kompis
najyk najyk
joostvdl joostvdl
berdir berdir
EtienneRd EtienneRd
harrrrrrr harrrrrrr
czigor czigor
xaa xaa
weri weri
akalam desarrollo2.0
Photoshopper Photoshopper
antims antims
lamp5 lamp5
pikot pikot
smithmilner smithmilner volunteering
dandaman dandaman
drupalfan2 drupalfan2 volunteering
keynone keynone
sven.lauer sven.lauer
jose reyero reyero
ludo.r dolu
gerson.analista gerson.analista
stefan.r stefan.r
daniel korte danielkorte organization(s): TOKY Branding + Design
joseph.olstad joseph.olstad
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.