Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
xjm volunteering organization(s): Acquia, xjm
heddn organization(s): MTech, LLC
cilefen
mrf
johnshortess
rklawson
bburg
baisong volunteering
jibran volunteering
metzlerd volunteering
gapple volunteering
phillamb168 volunteering
duaelfr volunteering organization(s): Happyculture
akalata volunteering
yesct
prasad_gogate organization(s): Acquia
nagwani organization(s): Acquia
saitanay volunteering organization(s): Acquia
swarad07 organization(s): Blisstering Solutions
mikeryan organization(s): Virtuoso Performance customer(s): North Studio
pwolanin volunteering organization(s): SciShield
jcl324 volunteering
capysara
wturrell volunteering
shaal volunteering
rachel_norfolk organization(s): Open Development Ltd customer(s): Horizons Unlimited
fgm volunteering organization(s): OSInet
ekl1773 volunteering
benjifisher organization(s): Isovera customer(s): Pegasystems
joelpittet volunteering organization(s): The University of British Columbia
volkswagenchick organization(s): Kanopi Studios
hitesh-jain organization(s): Acquia
aditya.ghan organization(s): Blisstering Solutions
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.