Issue
Contribution records
Contributors

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

Give credit to everyone
larowlan organization(s): PreviousNext
smustgrave organization(s): Mobomo
anybody volunteering organization(s): DROWL.de
cozydrupalnerd volunteering
bbu23 organization(s): Ninja Coders
gatiba
nitesh624
jphelan
ed2908
lorenzs volunteering
nikathone organization(s): JSI Research & Training Institute, Inc. (JSI) customer(s): JSI Research & Training Institute, Inc. (JSI)
boregar
shivam_tiwari organization(s): Innoraft
svicer organization(s): ITCare
nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
ahmad khader organization(s): Vardot
thomas kaisuka volunteering organization(s): Century Marvel Digital Solutions
manibharathi ezhimalai ravi organization(s): Material
karenann
ianwesty organization(s): BBC Worldwide
jhan1112 organization(s): Full Fat Things
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.