Contribution records
Contributors

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

Give credit to everyone
johnwebdev johnwebdev
mrweiner mrweiner volunteering
twfahey twfahey volunteering organization(s): University of Texas at Austin
borisson_ borisson_ organization(s): Calibrate
yogeshmpawar yogeshmpawar organization(s): QED42
alexpott alexpott organization(s): Thunder
joegraduate joegraduate organization(s): The University of Arizona
mitthukumawat mitthukumawat volunteering organization(s): Zyxware Technologies customer(s): Drupal Association
dcam dcam
quietone quietone organization(s): PreviousNext
smustgrave smustgrave organization(s): Mobomo
uniquename uniquename
firewaller firewaller
ismail cherri IsmailCherri volunteering
tim.plunkett tim.plunkett organization(s): Acquia
adam-delaney adam-delaney
james hawthorn-byng JamesByng
luke.leber lleber
ravi.shankar ravi.shankar organization(s): OpenSense Labs
matthiasm11 matthiasm11 organization(s): Randstad Digital
jastraat jastraat organization(s): CivicActions, Centers for Medicare and Medicaid Services customer(s): Centers for Medicare and Medicaid Services
bkosborne bkosborne
catch catch organization(s): Third and Grove
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.