Issue
Contribution records
Contributors

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

Give credit to everyone
nicxvan organization(s): nLightened Development LLC
camoa organization(s): Palcera
chadhester volunteering organization(s): Mindyte
chrisfromredfin organization(s): Redfin Solutions, LLC
dries
flux423 volunteering organization(s): BLUEFLY.IO LLC
froboy organization(s): ImageX
hestenet organization(s): Drupal Association
johnpicozzi organization(s): EPAM
jonas139 organization(s): iO
joshuami
jpamental organization(s): Isovera
jrockowitz volunteering organization(s): The Big Blue House, Webform module Open Collective
jurgenhaas organization(s): LakeDrops
kevinquillen organization(s): Velir
lostcarpark volunteering
mandclu volunteering organization(s): Acquia
mglaman organization(s): Acquia
stephencross volunteering
teknorah organization(s): tekNorah customer(s): BLUEFLY.IO LLC, MidCamp
tonytosta
ultimike organization(s): DrupalEasy
yautja_cetanu
steven jones organization(s): ComputerMinds
tim d. organization(s): Drupal Association
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.