Issue
Contribution records
Contributors

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

Give credit to everyone
peregrine
modiphier
smiklos
woodp
MadOverlord
spiney
mike_san
gozigzag
t3rtle
ergow
izmeez
Yasmina7575
marjory
heine
David_Rothstein volunteering
awakash
jzornig
PipB
heatherwoz
Bizio
chartmann
kpyan8s
Wtower
tregonia
iaha
GoddamnNoise
sa3z
tjmcgraw
dashaver
McSukkelaar
kristiaanvandeneynde
ceo314
deanflory
equipages
jeseich volunteering
ranjith_kumar_k_u organization(s): Zyxware Technologies
nikhil_110 organization(s): Material
Jorge Campo
zap-admin
suffering drupal
christopher james francis rodgers
bcobin
quietone organization(s): PreviousNext
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.