Issue
Contribution records
Contributors

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

Give credit to everyone
bgreco
cilefen organization(s): Institute for Advanced Study
dwebpoint organization(s): EPAM
sergei_brill volunteering
efrainh organization(s): Evolving Web
szeidler organization(s): Ramsalt Lab
phenaproxima organization(s): Acquia
seanb
larowlan organization(s): PreviousNext
kbrodej organization(s): Agiledrop - Your Trusted Drupal Teammates
mqanneh volunteering organization(s): Chronos Interactive Media
quietone organization(s): PreviousNext
wwedding organization(s): Sticky Co
aschiwi organization(s): undpaul
ameymudras organization(s): Salsa Digital
sjerdo organization(s): Synetic
deepalij organization(s): Salsa Digital
smustgrave organization(s): Mobomo
sharique volunteering customer(s): Drupal India Association
rajab natshah organization(s): Vardot customer(s): Vardot
anup.singh volunteering customer(s): Faichi Solutions Pvt Ltd
Manibharathi E R organization(s): Material customer(s): Material
gaurav-mathur organization(s): Dotsquares Ltd.
nick dewitte
a.dmitriiev volunteering organization(s): 1xINTERNET
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.