Contribution records
Contributors

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

Give credit to everyone
magico magico
matt_paz mattpaz
RobRoy robroy
souvent22 souvent22
pcorbett pcorbett
dmitrig01 dmitrig01
Watcherq Watcherq
silurius silurius
dries dries
NaX nax
allisterbeharry allisterbeharry
hswong3i hswong3i
antgiant antgiant
natcolley natcolley
iseyfi iseyfi
sachand sachanda
Crell Crell
chx chx
catch catch
seanr seanr
jrabeemer Giovanni_Glass
Broicher Broicher
ryanhunt ryanhunt
hpcalaf hpcalaf
italent italent
alexanderpas alexanderpas
develcuy develCuy
verta verta
geste geste
ashayc ashayc
sriniko sriniko
ton_cut345 ton_cut345
bkdrupal kbalajimca
imorris imorris
moshe weitzman weitzman
rok žlender rokZlender
boris mann borismann
damien tournoud damz
alexander allen AlexanderAllen
hass hass
quietone 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.