Issue
Contribution records
Contributors

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

Give credit to everyone
fago organization(s): drunomics
tedbow organization(s): Acquia
matt_paz
acbramley organization(s): PreviousNext customer(s): Service NSW
smustgrave organization(s): Mobomo
catch organization(s): Third and Grove
dcam organization(s): USDA-ARS
danielveza volunteering organization(s): PreviousNext
arakwar
tim.plunkett organization(s): Acquia
ravi.shankar organization(s): OpenSense Labs
neslee canil pinto organization(s): Specbee
kim.pepper organization(s): PreviousNext
akram khan volunteering organization(s): Material customer(s): Drupal India Association
oily volunteering organization(s): Cactus Blossom IT Services Limited
volkswagenchick volunteering
larowlan organization(s): PreviousNext
godotislate 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.