Contribution records
Contributors

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

Give credit to everyone
ady1503 ady1503 volunteering
goz goz organization(s): Barbe-Rousse, Iosan
izus izus
pgn5qs pgn5qs
greatmatter greatmatter
wheelercreek wheelercreek volunteering
steveoriol steveoriol organization(s): Netxtime
emmguyot emmguyot-adscom
protitude protitude volunteering
zany zany
rwam rwam
somersoft somersoft
yurg yurg volunteering
kris77 Kris77
marcoliver marcoliver organization(s): publicplan GmbH
adrianliegmann AdrianLiegmann organization(s): Droptica
joelseguin joelseguin volunteering
srinivasraod srinivasraod
leducdubleuet LeDucDuBleuet
kreatil kreatIL
davedg629 davedg629
shyam-sawhney shyam-sawhney volunteering
jepster_ jepSter organization(s): publicplan GmbH
ambient.impact Ambient.Impact organization(s): Consensus Enterprises
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.