Contribution records
Draft
Contributors

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

Give credit to everyone
jondblackburn jondblackburn
PixelClever aaronhawkins
yhancik yhancik
miiimooo miiimooo
krisrobinson krisrobinson
drupalninja99 jaykali
duckzland victheme
ashiwebi ashiwebi
adam_b adam_b
digitalfrontiersmedia DigitalFrontiersMedia
TimG1 TimG1
grego3781 grego3781
kdhartstrom kdhartstrom
oddhenrik oddhenrik
rilsonraposo rilsonraposo
anybody Anybody
nubeli nubeli
yochee yochee
CarbonPig CarbonPig
mesch Chrysalis
massud massud
summit summit
essbee essbee
aa461 aa461
amysiano4x3 amysiano4x3
hillaryneaf nektir
1mundus 1mundus
ranx ranx
jeepster jeepster
crutch crutch
adanielyan adanielyan
elliot elliot
abarpetia abarpetia
Rob T Rob_T
arx-e arx-e
pat redmond PatRedmond
brst t brstt
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.