Contribution records
Draft
Contributors

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

Give credit to everyone
dawehner dereine volunteering
larowlan larowlan organization(s): PreviousNext customer(s): Service NSW
dagmar dagmar organization(s): Globant
naveenvalecha naveenvalecha volunteering organization(s): Acquia
jibran jibran organization(s): PreviousNext customer(s): University of Technology, Sydney
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
catch catch organization(s): Third and Grove
joelpittet joelpittet
berdir berdir organization(s): MD Systems GmbH
paulocs paulocs organization(s): CI&T
mohit_aghera mohit_aghera volunteering organization(s): Axelerant
nishantghetiya nishantghetiya volunteering organization(s): QED42 customer(s): Drupal India Association
sudiptadas19 dsudipta1249 organization(s): QED42 customer(s): Drupal India Association
ilgnerfagundes ilgnerfagundes organization(s): CI&T
andypost andypost volunteering organization(s): Skilld
quietone quietone organization(s): PreviousNext
les lim lesmana
star-szr star-szr volunteering
shivam kaushal shivam_kaushal organization(s): OpenSense Labs
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.