Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
tedbow organization(s): Acquia
alexpott organization(s): Acro Commerce, Thunder
larowlan organization(s): PreviousNext
chi
catch organization(s): Third and Grove
yoroy organization(s): Roy Scholten
ressa organization(s): Ardea
pasqualle volunteering
g089h515r806
Mixologic organization(s): Drupal Association
effulgentsia organization(s): Acquia
aaronmchale volunteering
matthieuscarset volunteering
lauriii organization(s): Acquia
2dareis2do
drumm organization(s): Drupal Association
nod_ volunteering organization(s): Très Bien Tech customer(s): Liip, Palantir.net, Vardot
quietone organization(s): PreviousNext
poker10 organization(s): ActivIT s.r.o.
kristen pol customer(s): Hook 42
gábor hojtsy organization(s): Acquia
wim leers organization(s): Acquia
grimreaper organization(s): Smile
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.