Contribution records
Contributors

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

Give credit to everyone
criscom criscom
zessx zessx
meichr meichr volunteering
gge gge
ollioi ollioi
rv0 rv0 organization(s): Coworks.be customer(s): Coworks.be
ranx ranx
anybody Anybody organization(s): DROWL.de
tstoeckler tstoeckler volunteering
keszthelyi keszthelyi
4c2o 4c2o volunteering
leonq leonq
yazzbe yazzbe volunteering
ikaros123 ikaros123
timme77 timme77
jukka792 jukka792 volunteering
morphay morphay
grinxols grinxols
finex finex volunteering
grayle Grayle organization(s): Dropsolid
cegascam cegascam
Neli Neli
ram4nd ram4nd volunteering
handkerchief handkerchief organization(s): RealizationZone
drupaldope drupaldope
anaconda777 anaconda777 volunteering
menwithbeards menwithbeards
sahil khambra sahilkhambra volunteering organization(s): Trigyn Technologies Ltd
Beatriz Cunha Beatriz Cunha
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.