Issue
Contribution records
Contributors

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

Give credit to everyone
markconroy organization(s): Annertech customer(s): Limerick City & County Council
zerolab organization(s): Torchbox
fabianx volunteering organization(s): Tag1 Consulting, Inc.
lauriii organization(s): Druid
catch organization(s): Third and Grove
kbeck303 organization(s): Oomph, Inc.
bdanin
kerby70 organization(s): JAKALA (formerly FFW)
alexpertsi
mlncn volunteering organization(s): Agaric customer(s): Cambridge, Massachusetts Family Policy Council, Drutopia, Find It Cambridge
ptmkenny
jedgar1mx
swirt organization(s): CivicActions customer(s): Department of Veterans Affairs
shamsher_alam
enrico.sato organization(s): SparkFabrik
vadim.jin
stefan.korn organization(s): Stefan Korn - Webentwicklung
amir jamshidi
gaëlg organization(s): Insite
alex.bukach
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.