Contribution records
Contributors

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

Give credit to everyone
lewisnyman lewisnyman
Reinmar Reinmar
Bojhan bojhan volunteering
sarah_p sarah_p
darketaine darketaine volunteering organization(s): Pixual
tic2000 tic2000 organization(s): Intellix
davidhernandez davidhernandez organization(s): JAKALA (formerly FFW)
ironkiat ironkiat organization(s): Pixel Onion Pte Ltd
thpoul thpoul volunteering organization(s): Pixual
kostyashupenko kostyashupenko organization(s): Skilld
catch catch organization(s): Third and Grove
himanshugautam himanshugautam
yoroy yoroy organization(s): Roy Scholten
webchick webchick organization(s): Acquia
wim leers wimleers organization(s): Acquia
star-szr star-szr volunteering organization(s): Northern Commerce
emma.maria emma.maria organization(s): TES Global
rajab natshah RajabNatshah organization(s): Vardot
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.