Issue
Contribution records
Contributors

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

Give credit to everyone
yolker
RemyAroundTown
chiranjeeb2410 organization(s): Google Summer of Code
oeklesund organization(s): JAKALA (formerly FFW)
ethomas08 volunteering
alonaoneill organization(s): Hook 42
pcate
kostyashupenko organization(s): Skilld
cilefen organization(s): Institute for Advanced Study
pameeela
ranjith_kumar_k_u organization(s): Zyxware Technologies
quietone volunteering organization(s): PreviousNext
jofitz
gauravvvv organization(s): OpenSense Labs customer(s): Drupal India Association
longwave organization(s): Full Fat Things
vsujeetkumar organization(s): Material customer(s): Drupal India Association
smustgrave organization(s): Mobomo
darvanen
wim leers organization(s): Acquia
hershey.k volunteering
yedhukrishnan.p@valuebound.com organization(s): Valuebound customer(s): Valuebound
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.