Contribution records
Draft
Contributors

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

Give credit to everyone
mikeytown2 mikeytown2
ogi ogi
EndEd EndEd
drupa11y marcus.morba
tebb Dru-p
acoustika acoustika
Barfly Barfly
ss81 ss81
jeffwidman jeffwidman
obrienmd obrienmd
benrogmans benrogmans
tripper54 tripper54
sachbearbeiter sachbearbeiter
Fidelix Fidelix
skizzo skizzo
mikefyfer mikefyfer
roam2345 jucallme
elianm elianm
virtuali1151 virtuali1151
socialnicheguru SocialNicheGuru
darrenlambert darrenlambert
funana funana
mgifford mgifford
sylv3st3r sylv3st3r
omega8cc omega8cc
giorgio79 giorgio79
yannickoo yannickoo
Bhanuji Bhanu
janis_lv janis_lv
rooby rooby
sah62 sah62
nwom nwom
geek-merlin geek-merlin
ar-jan ar-jan
sam moore SamMoore
janel-1 janel-1
podarok podarok
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.