Issue
Contribution records
Contributors

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

Give credit to everyone
dagmar organization(s): Globant
rajeshwari10 volunteering organization(s): Blisstering Solutions
jhodgdon
arkiii organization(s): Multimedia Partners
ronchica volunteering
cilefen
leslieg volunteering
xjm organization(s): Acquia
tameeshb organization(s): Google Summer of Code
abi_cima volunteering organization(s): Globant
jacobsanford volunteering
valthebald
mikeohara
dhruveshdtripathi organization(s): DevsAdda
catch organization(s): Third and Grove
dinesh18 volunteering
vaibhav29
yoroy organization(s): Roy Scholten
avpaderno volunteering
ranjith_kumar_k_u organization(s): Zyxware Technologies
selwynpolit
ijf8090 volunteering
chrisdarke volunteering
kapilv volunteering organization(s): Innoraft customer(s): Drupal Association, Drupal Care
kleiton_rodrigues organization(s): CI&T
longwave organization(s): Full Fat Things
larowlan organization(s): PreviousNext
rakesh.gectcr volunteering organization(s): Valuebound
gaurav.kapoor organization(s): OpenSense Labs
c.nish2k3 volunteering
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.