Contribution records
Contributors

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

Give credit to everyone
m4olivei m4olivei organization(s): Lullabot
finnsky finnsky organization(s): Skilld
nod_ nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
rinku jacob 13 RinkuJacob13 organization(s): Material customer(s): Drupal India Association
keshav patel Keshav organization(s): Dassault Systèmes
shweta__sharma shwetaoti organization(s): OpenSense Labs
sandip sandip_poddar organization(s): Innoraft
divya.sejekan divya.sejekan organization(s): QED42 customer(s): Drupal India Association
smustgrave smustgrave organization(s): Mobomo
jensdn jensdn
rachel_norfolk rachel_norfolk
ckrina ckrina
catch catch organization(s): Third and Grove
lauriii lauriii organization(s): Acquia
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.