Issue
Contribution records
Contributors

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

Give credit to everyone
drifter
klausi
Crell organization(s): Palantir.net
donutdan4114
superspring
rob3000
sun
grom358
damiankloip
webchick
pwolanin
ParisLiakos
andypost
dawehner volunteering organization(s): Tag1 Consulting, Inc.
jhodgdon
geerlingguy
hussainweb organization(s): Axelerant
bojanz
jcnventura volunteering
joelpittet organization(s): The University of British Columbia
xjm organization(s): Acquia
pfrenssen
tizzo
kenorb
perignon volunteering
NerOcrO organization(s): Axess Open Web Services
droplet
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
chi
dbt102
David_Rothstein volunteering
effulgentsia organization(s): Acquia
drunken monkey volunteering
alex.skrypnyk volunteering
hass
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.