Issue
Contribution records
Contributors

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

Give credit to everyone
cilefen
ashwinparmar
tameeshb organization(s): Google Summer of Code
ideaseed
pancho volunteering
finex volunteering
sam152 organization(s): PreviousNext
alternativo volunteering
anushrikumari organization(s): OpenSense Labs
tanubansal organization(s): Salsa Digital
vikashsoni volunteering organization(s): Zyxware Technologies
danflanagan8 organization(s): Horizontal
gtoyloy18 volunteering
quietone organization(s): PreviousNext
asad_ahmed organization(s): OpenSense Labs
tiwariraj91929 volunteering
idebr organization(s): iO
priscarabelli organization(s): Pivale
smustgrave organization(s): Mobomo
alexpott organization(s): Acro Commerce, Thunder
catch organization(s): Third and Grove
sugaroverflow
archana.phatangare organization(s): QED42 customer(s): Drupal India Association
sourabh.singhal volunteering organization(s): Faichi Solutions Pvt Ltd customer(s): Faichi Solutions Pvt Ltd
andrew answer
aarti zikre volunteering organization(s): QED42
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.