Contribution records
Contributors

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

Give credit to everyone
mcdruid mcdruid
juampynr juampy organization(s): Lullabot
mariacha1 mariacha organization(s): ThinkShout
jasonawant jwant organization(s): Current
gambry gambry organization(s): manifesto
mparker17 mparker17 organization(s): Cool Blue Interactive
sanduhrs sanduhrs organization(s): erdfisch
rodrigoaguilera rodrigoaguilera organization(s): Ymbra
snehi snehi volunteering organization(s): Publicis Sapient customer(s): Publicis Sapient
jofitz jofitz organization(s): ComputerMinds
catch catch organization(s): Third and Grove
xsdx dalibor_stojakovic organization(s): Websolutions Agency
tim.plunkett tim.plunkett volunteering
tobias.grasse tobias.grasse customer(s): undpaul
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.