Issue
Contribution records
Contributors

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

Give credit to everyone
patrickmichael
mrweiner organization(s): Flat 9
cilefen
gnumatrix
hansfn
gillesbailleux volunteering
ConradFlashback
nottaken
dolst volunteering
_gramur
borisbarowski volunteering
szato volunteering organization(s): Brainsum customer(s): diginomica
DropInTheOcean volunteering
ttnt
catch organization(s): Third and Grove
plessas
propercroc volunteering
francoud volunteering
parijke
lingros
rafageist volunteering
mfb
john_b
xjm organization(s): Acquia
berdir organization(s): MD Systems GmbH
andypost volunteering organization(s): Skilld
benjifisher volunteering organization(s): FRUITION
kraut volunteering
phenaproxima organization(s): Acquia
rkoller
mullzk
lauriii volunteering
gambry organization(s): EPAM
jppo
rfmarcelino
bogdog400 volunteering
john.glynn.davies volunteering
didier misson volunteering
Cynthia Ewer
petr illek volunteering
ravi.shankar organization(s): OpenSense Labs
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.