Contribution records
Draft
Contributors

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

Give credit to everyone
heddn lucashedding organization(s): MTech, LLC, Tag1 Consulting, Inc.
catch catch organization(s): Third and Grove
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
alexpott alexpott organization(s): Acro Commerce, Thunder
anmolgoyal74 anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
neclimdul neclimdul organization(s): APQC
bradjones1 bradjones1 organization(s): Big Island Fish
kapilv kapilkumar0324 volunteering organization(s): Innoraft customer(s): Drupal Association, Drupal Care
rgpublic rgpublic
mstrelan mstrelan organization(s): PreviousNext
ankithashetty AnkShetty volunteering organization(s): Specbee
andypost andypost volunteering organization(s): Skilld
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
longwave longwave organization(s): Full Fat Things
ravi.shankar ravi.shankar organization(s): OpenSense Labs
suresh prabhu parkala SureshPrabhuParkala organization(s): Specbee
wim leers wimleers organization(s): Acquia
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
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.