Contribution records
Contributors

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

Give credit to everyone
kristiaanvandeneynde kristiaanvandeneynde organization(s): Deeson, Factorial.io
bojanz bojanz organization(s): Centarro
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
psf_ psf_ organization(s): SDOS
larowlan larowlan volunteering organization(s): PreviousNext
askibinski askibinski organization(s): iO customer(s): Erasmus University Rotterdam
solimanharkas SolimanHarkas organization(s): Factorial.io
mohit_aghera mohit_aghera organization(s): QED42
vsujeetkumar vsujeetkumar organization(s): Material customer(s): Drupal India Association
idebr idebr organization(s): iO
smustgrave smustgrave organization(s): Mobomo
tstoeckler tstoeckler volunteering organization(s): resc.
quietone quietone organization(s): PreviousNext
alexpott alexpott organization(s): Acro Commerce, Thunder
oily andrewfarq volunteering organization(s): Cactus Blossom IT Services Limited
ravi.shankar ravi.shankar organization(s): OpenSense Labs
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.