Contributors

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

Give credit to everyone
seantwalsh seantwalsh
bendygirl bendygirl
cecilialevy CeciliaLevy
froboy froboy volunteering organization(s): MidCamp
gargsuchi gargsuchi organization(s): Salsa Digital
hestenet hestenet organization(s): Drupal Association
jitka_pilar jitka_pilar
johnpicozzi johnpicozzi organization(s): EPAM
leslieg lglynn2299 organization(s): Redfin Solutions, LLC
volkswagenchick volkswagenchick organization(s): The Linux Foundation
weekbeforenext weekbeforenext
darren oh darrenoh organization(s): Cognizant Softvision customer(s): Estée Lauder Companies
imre gmelig meijling imre_gmelig_meijling volunteering organization(s): ronder
kristen pol kepol organization(s): Itty Bitty Byte customer(s): Salsa Digital
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.