Contribution records
Contributors

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

Give credit to everyone
mgriego mgriego
dddave dddave
bleen bleen18
drupal_was_my_past rocket
droplet droplet
dcam dcam
meeli meeli
gsharm gsharm organization(s): Material
ifrik ifrik
latikas latika_surse
duaelfr DuaelFr volunteering organization(s): Happyculture
paulmartin84 paulmartin84
danharper danharper volunteering organization(s): Curve Agency
danylevskyi danylevskyi volunteering
nlisgo nlisgo
alimac alimac organization(s): University of Illinois at Chicago
pektinasen pektinasen
fatfish fatfish volunteering organization(s): FatFish
yesct YesCT
webchick webchick organization(s): Acquia
realityloop realityloop volunteering organization(s): Realityloop
susanb susanb
aburrows abdesignuk volunteering
alvar0hurtad0 alvar0hurtad0 organization(s): ASPgems
john cook johncook
trupti bhosale Truptii organization(s): Axelerant
anil.gangwal gangwalanil volunteering organization(s): Publicis Sapient customer(s): Publicis Sapient
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.