Contribution records
Contributors

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

Give credit to everyone
davidburns davidburns volunteering
jhedstrom jhedstrom organization(s): Phase2
avpaderno avpaderno volunteering
pobster pobster organization(s): ArcadeGeek LTD customer(s): Rackspace
mbovan mbovan organization(s): MD Systems GmbH
berdir berdir organization(s): MD Systems GmbH
edwardchiapet edwardchan organization(s): Current
dimilias dimilias organization(s): Randstad Digital customer(s): European Commission and European Union Institutions, Agencies and Bodies
karens karens
martijn de wit martijndewit organization(s): Ablerz
claudiu.cristea claudiucristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
it-cru it-cru
luke.leber lleber volunteering
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.