Contribution records
Contributors

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

Give credit to everyone
gargsuchi gargsuchi organization(s): Salsa Digital
ameymudras mudrasamey organization(s): Salsa Digital
flicstar flicstar
fubarhouse fubarhouse organization(s): amazee.io
gg24 gg24 volunteering organization(s): Salsa Digital
ivrh cms-drupal-training organization(s): Salsa Digital
jannakha jannakha organization(s): Tomato Elephant Studio customer(s): Must Do Brisbane, ROCKCOTE
jct321 JCT321 volunteering
kobusvw kobusvw
kurtfoster kafmil volunteering organization(s): Department of Premier and Cabinet - Victoria, Australia
paulmorriss paulmorriss organization(s): Salsa Digital
realityloop realityloop volunteering organization(s): Realityloop
richardgaunt RichardGaunt organization(s): Salsa Digital
singularo singularo organization(s): Aussie Angels
trandy1981 trandy1981
tyler36 tyler36 organization(s): Inter Quest Co.,Ltd.
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
xamount xamount organization(s): Salsa Digital
govind.maloo govind.maloo organization(s): Salsa Digital
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.