Issue
Contribution records
Contributors

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

Give credit to everyone
johnlutz organization(s): Cheeky Monkey Media, Promet Source
swentel organization(s): eps & kaas customer(s): Dropsolid
drcolossos organization(s): CYLEDGE
oknate volunteering
weynhamz organization(s): CI&T
alison volunteering
komejo
jorgegc volunteering
peterwcm
plato1123
scoff
phenaproxima organization(s): Acquia
fabiansierra5191 volunteering organization(s): Mobomo
baluertl organization(s): Cheppers
purefoxy
jhedstrom organization(s): Phase2
tobiasb volunteering
gregrholden
cgmonroe volunteering
eric_a organization(s): Dutch Open Projects, RIVM
neclimdul organization(s): APQC
tjmoyer organization(s): Mindgrub Technologies
acbramley organization(s): PreviousNext customer(s): Service NSW
wim leers organization(s): Acquia
sun-fire
liam morland organization(s): OpenPlus, Scouting Waterloo Region
joseph.olstad organization(s): Cinder Systems Corp., Entreprise 7pro.ca Inc
dave reid volunteering organization(s): Lullabot
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.