Issue
Contribution records
Contributors

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

Give credit to everyone
nesta_
pcambra organization(s): Cambrico
fjgarlin volunteering organization(s): Drupal Association
niteman organization(s): sbit.io customer(s): sbit.io
solucionex
oskar_calvo
aarnau organization(s): hiberus
agarciadomen
amartinezlabrador
d70rr3s organization(s): hiberus
igonzalo organization(s): hiberus
joseminosa
julianvj organization(s): hiberus
rapindrive
mon_franco organization(s): NTT DATA
isholgueras volunteering organization(s): Lullabot
diegocg
dgaspara organization(s): NTT DATA
raqfialho organization(s): NTT DATA
alvar0hurtad0
penyaskito organization(s): Lingotek
idiaz.roncero customer(s): La Cañamería Global S.L.
manuel.adan organization(s): NTT DATA
J.Lu volunteering organization(s): NTT DATA
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.