Issue
Contribution records
Contributors

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

Give credit to everyone
ceardach
redijedi
mpaler
brianV
xano
catch
starscream
tstoeckler
bassplaya
izmeez
tchurch
petednz
robbdavis
timofey
duaelfr
boombatower
amontero
hefox
yesct
univate
babruix
stpaultim
shariharan
disasm
shnark
bookmarvel
sun
alexpott
chx
mtift
jenlampton organization(s): Jeneration Web Development customer(s): Nursing Schools Alamanac
sinasalek
eiriksm organization(s): Ny Media AS
zaporylie
David_Rothstein volunteering
xjm organization(s): Acquia
MaskOta
IRuslan volunteering organization(s): DrupalJedi
PascalAnimateur
andrewfn volunteering
joegraduate organization(s): The University of Arizona
genellann
poker10 organization(s): ActivIT s.r.o.
quietone volunteering
justaman volunteering
Alan.Guggenheim
rob c
star-szr
alan d.
alex.skrypnyk volunteering organization(s): DrevOps
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.