Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
tekante
febbraro
carlos8f
bfroehle
W32
sun
pillarsdotnet
jbrown
xjm
bradhawkins
catch
bvanmeurs
kathyh
joelcollinsdc
KingSalibah
chx
donquixote
ufku
damienmckenna
tomogden
andypost
batje
mukhsim
Leeteq
ianthomas_uk
RunePhilosof
ekl1773
mradcliffe
ciss
geerlingguy
bdone
agerson
jtk23
yesct
alesr
developerchris volunteering
cka3o4h1k
mickaelperrin volunteering
nwom
kopeboy volunteering
rbrissaud
jonathanshaw
moonray organization(s): Chapter Three (acquired by Kanopi Studios)
Yaazkal
hargobind volunteering
kmajzlik organization(s): Ciklum Western Europe
hmartens
murz
ccarnnia
aleevas organization(s): Skilld
daveiano volunteering
apermuy
solideogloria
ptmkenny
jimconte
avpaderno volunteering
artusamak organization(s): Happyculture
moshe weitzman
tim.plunkett
honza pobořil
Pavan B S organization(s): Valuebound
ravi.shankar organization(s): OpenSense Labs
prudloff organization(s): Insite
cmlara volunteering organization(s): DM13 Security LLC
liam morland volunteering organization(s): OpenPlus, Scouting Waterloo Region
pdureau organization(s): Beyris
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.