Issue
Contribution records
Contributors

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

Give credit to everyone
ydahi
ecvandenberg volunteering
xjm organization(s): Acquia
kferencz91
ttnt
littlepixiez volunteering
nickgee
greggles organization(s): Morris Animal Foundation
cilefen organization(s): Institute for Advanced Study
emerham volunteering
tim_dj
alexpott organization(s): Acro Commerce, Thunder
benjifisher organization(s): Isovera
floown
dsnopek organization(s): myDropWizard
cms_macgyver volunteering
skin
bryangullan volunteering
jlockhart
fabianx volunteering
pbirk
cnelsonakgov
pandaski organization(s): govCMS (Australian Government Department of Finance)
ressa organization(s): Ardea
generalredneck organization(s): Four Kitchens
Hitby
piridium volunteering
damienmckenna organization(s): Current
nchase volunteering
asb volunteering
greg.1.anderson organization(s): Pantheon
samuel.mortenson volunteering
moshe weitzman
Alex Monaghan 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.