Contribution records
Contributors

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

Give credit to everyone
WidgetsBurritos davidstinemetze organization(s): Rackspace
shaal shaal volunteering organization(s): Palantir.net
brianperry backlineint organization(s): Bounteous
duaelfr DuaelFr volunteering organization(s): Happyculture
saschaeggi saschaeggi volunteering
lauriii lauriii organization(s): Acquia
nitesh624 nitesh624 volunteering organization(s): Material customer(s): Drupal India Association
mherchel mherchel
mgifford mgifford organization(s): OpenConcept Consulting Inc.
andrewmacpherson andrewmacpherson volunteering
anmolgoyal74 anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
kapilv kapilkumar0324 volunteering organization(s): Innoraft customer(s): Drupal Association, Drupal Care
anushrikumari anushri19 organization(s): OpenSense Labs
catch catch organization(s): Third and Grove
xjm xjm organization(s): Acquia
alexpott alexpott organization(s): Acro Commerce, Thunder
kiran.kadam911 kiran.kadam911 organization(s): QED42 customer(s): Drupal India Association
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.