Contribution records
Contributors

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

Give credit to everyone
aneek aneek volunteering
serg2 serg2
snehi snehi volunteering organization(s): Publicis Sapient customer(s): Publicis Sapient
droplet droplet
anil280988 anil280988 organization(s): Publicis Sapient customer(s): Publicis Sapient
nod_ nod_ volunteering
tic2000 tic2000 organization(s): Intellix
sumthief ShlyapkinGrigoriy volunteering organization(s): DrupalJedi
msankhala msankhala
guypaddock guypaddock organization(s): Inveniem
larowlan larowlan organization(s): PreviousNext
arunkumark arunkumark volunteering organization(s): Material customer(s): CodeExpertz
lendude Lendude organization(s): iO
manjit.singh Manjit.Singh organization(s): Material
wim leers wimleers volunteering organization(s): Acquia
sagar ramgade SagarRamgade volunteering
martijn de wit martijndewit organization(s): Ablerz
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.