Issue
Contribution records
Contributors

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

Give credit to everyone
sam152 volunteering organization(s): PreviousNext
tedbow organization(s): Acquia
bkosborne organization(s): Princeton University
acbramley organization(s): PreviousNext
poindexterous
azovsky
ethomas08 volunteering
pyrello organization(s): The University of Iowa
Oscaner organization(s): CI&T
edwardsay volunteering organization(s): AnyforSoft
beanjammin organization(s): Domain7
azinck
brooke_heaton volunteering
kyberman organization(s): Annertech
chrisolof organization(s): Greentech Renewables
chamilsanjeewa volunteering
robbt
smustgrave organization(s): Mobomo
larowlan organization(s): PreviousNext
xjm organization(s): Acquia
joshua1234511 organization(s): Salsa Digital
simgui8 volunteering
omahm
catch organization(s): Third and Grove
Webbeh organization(s): Georgia Institute of Technology
alexpott organization(s): Acro Commerce, Thunder
chris burge organization(s): University of Nebraska
tim.plunkett organization(s): Acquia
tyler-paavola volunteering
odai atieh organization(s): Vardot
kim.pepper organization(s): PreviousNext
rishi.kulshreshtha volunteering organization(s): Redfin Solutions, LLC
luke.leber
rajab natshah organization(s): Vardot customer(s): Vardot
kristen pol organization(s): Itty Bitty Byte customer(s): OPTASY
aarti zikre volunteering organization(s): QED42
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.