Contribution records
Contributors

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

Give credit to everyone
jelle_s jelles organization(s): District09
mahtab_alam mahtab_alam organization(s): Valuebound
msupko msupko
daggerhart daggerhart organization(s): Hook 42
loopduplicate loopduplicate
greggles greggles organization(s): CARD.com
tatarbj tatarbj organization(s): Petend
eescribanoc e.escribano organization(s): Youwe
adixb adambehnke
maskedjellybean maskedjellybean volunteering
tobiberlin tobiberlin organization(s): Abgeordnetenwatch
nimoatwoodway nimoatwoodway
markconroy MarkConroy organization(s): Annertech
greg boggs gregboggs
mahmoud barhouma Mahmoud.Barhouma
jepster_ jepSter
stephane aimar Staim organization(s): Smile
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.