Issue
Contribution records
Contributors

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

Give credit to everyone
ksenzee organization(s): Smartsheet
corbacho
alexpott
xjm organization(s): Acquia
klokie
sjager
TravisJohnston
pounard
jenlampton organization(s): Jeneration Web Development
damien_vancouver
ciss organization(s): yousign GmbH
joegraduate
David_Rothstein volunteering
Togas
DonofGor
droplet
criz volunteering organization(s): acolono GmbH
erykolryko
rkent_87
fabianx organization(s): Tag1 Consulting, Inc.
neograph734 volunteering
cilefen
catch organization(s): Third and Grove
k_zoltan organization(s): Cylex
jp.stacey organization(s): Magnetic Phield
nvaken
Shin-en
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.