Issue
Contribution records
Contributors

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

Give credit to everyone
catch organization(s): Third and Grove
mstrelan
acbramley organization(s): PreviousNext
spokje volunteering
nod_ organization(s): Très Bien Tech
effulgentsia organization(s): Acquia
chrisfromredfin organization(s): Redfin Solutions, LLC
fago organization(s): drunomics
pixelwhip organization(s): Aten Design Group
mglaman organization(s): Acquia
aangel organization(s): Performant Labs
larowlan organization(s): PreviousNext
deviantintegral organization(s): Lullabot
phenaproxima organization(s): Acquia
kevinquillen organization(s): Velir
the_g_bomb organization(s): Zoocha
murz volunteering organization(s): EPAM customer(s): EPAM
ressa organization(s): Ardea
wim leers organization(s): Acquia
nicxvan organization(s): nLightened Development LLC
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.