Contribution records
Contributors

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

Give credit to everyone
dasjo dasjo organization(s): Amazee Labs
fago fago organization(s): drunomics
klausi klausi
tassilogroeper pheadeaux
tormi tormi volunteering
fotidim fotidim
Pls Pls volunteering
hansfn hansfn
gge gge
kingfisher64 kingfisher64
mitchell mitchell
tr tr
graber Graber volunteering
rodmarasi rodmarasi
rooby rooby
dercheffe dercheffe
barrett barrett volunteering organization(s): Acquia
daffie daffie
andypost andypost volunteering organization(s): Skilld
jonathan1055 jonathan1055 volunteering
megachriz megachriz volunteering
c-logemann C-Logemann organization(s): paratio.com
geek-merlin geek-merlin organization(s): MachbarMacher
Adam Neutrik Adam Neutrik volunteering organization(s): MAROQQO studios
greg boggs gregboggs
clemens.tolboom clemenstolboom volunteering
freddy rodriguez Friedinand volunteering organization(s): Coresis
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.