Issue
Contribution records
Contributors

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

Give credit to everyone
adamps organization(s): AlbanyWeb
jonathanshaw
jofitz organization(s): ComputerMinds
larowlan organization(s): PreviousNext customer(s): University of Technology, Sydney
plach volunteering
lauriii organization(s): Acquia
nick_vh organization(s): Dropsolid
xjm organization(s): Acquia
aleevas organization(s): Skilld
sja112 organization(s): Material customer(s): Drupal India Association
mrpauldriver
duaelfr volunteering organization(s): Happyculture
catch organization(s): Third and Grove
spokje
alexpott organization(s): Thunder
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
benjifisher organization(s): FRUITION
andypost volunteering organization(s): Skilld
dpi organization(s): PreviousNext
delacosta456
imclean organization(s): Digital Ink
nigelcunningham organization(s): Technocrat
rinku jacob 13 organization(s): Zyxware Technologies
martijn de wit organization(s): Ablerz
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.