Contribution records
Draft
Contributors

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

Give credit to everyone
dawehner dereine volunteering
nod_ nod_ volunteering organization(s): Smile
a_thakur AshishThakur volunteering organization(s): Material
cilefen cilefen
sushantpaste ps_sushant organization(s): OSSeed Technologies
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
subhojit777 subhojit777 volunteering organization(s): Material
droplet droplet
mrinalini9 mrinalini9 organization(s): Material customer(s): Drupal India Association
snehalgaikwad SnehalG21 volunteering organization(s): QED42 customer(s): Drupal India Association
pratik_kamble pratik_kamble organization(s): QED42
samiullah samiullah organization(s): Salsa Digital
abhisekmazumdar abhisekmazumdar volunteering organization(s): QED42 customer(s): Drupal India Association
trupti bhosale Truptii organization(s): Axelerant
wim leers wimleers volunteering organization(s): Acquia
tim.plunkett tim.plunkett volunteering
raman.b ramanbatra1709 organization(s): OpenSense Labs
quietone quietone organization(s): PreviousNext
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.