Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
benjifisher volunteering organization(s): FRUITION, Tag1 Consulting, Inc.
aaronmchale volunteering
rkoller
smustgrave organization(s): Mobomo
larowlan organization(s): PreviousNext
lachlanj
camerongreen volunteering
mstrelan organization(s): PreviousNext
murrayw organization(s): Morpht
andypost volunteering organization(s): Skilld
legolasbo volunteering
MattA
eclipsegc
jct321 volunteering organization(s): Morpht
jimik42 organization(s): Morpht
marji organization(s): Morpht
pameeela organization(s): Technocrat
richo_au
rocketeerbkw volunteering
lauriii organization(s): Acquia
akalata organization(s): Tag1 Consulting, Inc.
generalredneck organization(s): Four Kitchens
ckrina organization(s): Lullabot
quietone volunteering
skipper-vp organization(s): Morpht
arctic.cheetah volunteering
gábor hojtsy organization(s): Acquia
jen.stein
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.