Contribution records
Contributors

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

Give credit to everyone
lobodakyrylo lobodakyrylo volunteering
mitthukumawat mitthukumawat volunteering organization(s): Zyxware Technologies customer(s): Drupal Association
lendude Lendude organization(s): iO
phthlaap phthlaap volunteering organization(s): Kyanon Digital
smustgrave smustgrave organization(s): Mobomo
pravesh_poonia Pravesh_Poonia organization(s): OpenSense Labs
quietone quietone organization(s): PreviousNext
codebymikey codebymikey organization(s): Zodiac Media
the_g_bomb the_g_bomb organization(s): Zoocha
vinmayiswamy VinmayiSwamy volunteering organization(s): Material customer(s): Drupal India Association
oily andrewfarq volunteering organization(s): Cactus Blossom IT Services Limited
johnv johnv
kumudb KumudB volunteering organization(s): Material
catch catch organization(s): Third and Grove
prudloff prudloff organization(s): Insite
chartmann carey.hartmann
p-neyens p-neyens organization(s): Sopra Steria
rtnilesh.gupta rtnilesh.gupta
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.