Contribution records
Contributors

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

Give credit to everyone
merlinofchaos merlinofchaos
geraldmelendez geraldmelendez
eyolf eyolf
danielbeeke danielbeeke
jlporter jlporter
arnaldoaa arnaldoaa
AlexisWilke alexiswilke
stoickthevast techwarrior
ParisLiakos rootatwc
nonliquet nonliquet
acbramley acbramley
paolomainardi paolomainardi
erlingx erlingx
mintonje mintonje
imkael imkael
benelori benelori
hassebasse hassebasse
develcuy develCuy organization(s): Dilygent
jentle07 jentle07
gmnowels gmnowels volunteering
opratr sirrion volunteering
Vikram Vikram volunteering
pdxgimlet pdxgimlet
rajkumar7it74 rajkumar7it74
oriol_e9g oriole9g organization(s): Diputació de Barcelona
zterry95 zterry95
darri darri
ownage ownage
Vikas.Kumar vks7056
jacobsta811 jacobsta811
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.