Contribution records
Contributors

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

Give credit to everyone
larowlan larowlan
andypost andypost
vijaycs85 vijaycs85
klonos klonos
eigentor eigentor
leehunter LeeHunter
yesct YesCT
batigolix batigolix
nick_schuch nick_schuch
dcmistry dcmistry
jhodgdon jhodgdon
pmackay pmackay
alexpott alexpott
jair jair
Bojhan bojhan
lisarex lisarex
tkoleary tkoleary
daffie daffie
sun sun
aspilicious aspilicious
webchick webchick
rodrigoaguilera rodrigoaguilera organization(s): Ymbra
xjm xjm organization(s): Acquia
hansfn hansfn
andrewmacpherson andrewmacpherson volunteering
quietone quietone organization(s): PreviousNext
smustgrave smustgrave organization(s): Mobomo
heather heather
gábor hojtsy goba organization(s): Acquia
kristen pol kepol
clemens.tolboom clemenstolboom volunteering
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
electric doorknob Electric_Doorknob volunteering
Git commit message
Commit types
  • 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

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.