Issue
Contribution records
Contributors

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

Give credit to everyone
almunnings
coffeemakr volunteering
pearls
mlncn organization(s): Agaric customer(s): Drutopia
niklp
fuchoa volunteering
marieascomedia
justcaldwell volunteering
lifelifeone organization(s): Adimeo
felipep
joevagyok organization(s): European Commission and European Union Institutions, Agencies and Bodies customer(s): European Commission and European Union Institutions, Agencies and Bodies
dalemoore
gorkagr organization(s): Erasmus Student Network
grevil volunteering organization(s): DROWL.de
elisur organization(s): Seidor
trackleft2 volunteering organization(s): The University of Arizona
naidim volunteering
znerol
liquidcms
chr.fritsch organization(s): Thunder
ahmad abbad volunteering organization(s): Vardot customer(s): Vardot
rajab natshah organization(s): Vardot customer(s): Vardot
joaopauloc.dev organization(s): ImageX
nils.destoop volunteering
uri_frazier
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.