Issue
Contribution records
Contributors

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

Give credit to everyone
griffynh organization(s): PreviousNext
acbramley organization(s): PreviousNext customer(s): Service NSW
borisson_ volunteering organization(s): Calibrate
catch organization(s): Third and Grove
danflanagan8 organization(s): Horizontal
darvanen
dww organization(s): TEN7
jibran organization(s): Department of Customer Service, NSW
lendude organization(s): iO
quietone organization(s): PreviousNext
smustgrave organization(s): Mobomo
tinto organization(s): The Savvy Few
larowlan organization(s): PreviousNext
AkshayDalvi
akshaydalvi212 organization(s): QED42 customer(s): Drupal India Association
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
amber himes matz organization(s): Drupalize.Me
luke.leber volunteering
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.