Contribution records
Contributors

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

Give credit to everyone
tuwebo TuWebO organization(s): Metadrop
akalam desarrollo2.0 organization(s): Metadrop
borisson_ borisson_ organization(s): Calibrate
berliner berliner
attiks attiks organization(s): Attiks customer(s): United Nations
anfor pazairfog
hardikpandya Pandya-Hardik volunteering
jcisio jcisio volunteering organization(s): Axess Open Web Services customer(s): UNESCO
anneke_vde anneke_vde organization(s): iO
idebr idebr organization(s): iO
mkalkbrenner mkalkbrenner organization(s): Jarltech Europe GmbH
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.