Issue
Contribution records
Contributors

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

Give credit to everyone
nigelcunningham organization(s): Technocrat
alexpott organization(s): Acro Commerce, Thunder
catch organization(s): Third and Grove
plach volunteering
longwave organization(s): Full Fat Things
xjm organization(s): Acquia
gurunathan
xem8vfdh
brussam
mrpauldriver
siramsay volunteering
sashken2
cola
bogdog400 volunteering
prudloff organization(s): Insite
gwvoigt organization(s): Northern Commerce
tyler36
afagioli volunteering
joachim volunteering
fmb organization(s): Res Telæ
Estebancena
thirstysix volunteering organization(s): GTECH
aniketd volunteering
codeelegance
antcab
gopisathya
aldibier organization(s): SeeD EM
vagelis-prokopiou
ghost of drupal past organization(s): Smartsheet
orlando.thoeny organization(s): Namics customer(s): Namics
joseph.olstad
rajab natshah organization(s): Vardot customer(s): Vardot
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.