Issue
Contribution records
Contributors

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

Give credit to everyone
sam152 volunteering organization(s): PreviousNext
grimreaper organization(s): Smile
loze
andyf organization(s): Fabb customer(s): FRUITION, Sport Obermeyer
jacktonkin organization(s): ISSUP
hideaway organization(s): jobiqo - job board technology
scott_euser volunteering organization(s): Soapbox
romainj volunteering
anybody volunteering organization(s): DROWL.de
steinmb volunteering
jmagunia
smustgrave organization(s): Mobomo
joachim volunteering organization(s): Factorial.io
paul121
nod_ organization(s): Très Bien Tech
quietone organization(s): PreviousNext
nterbogt
m.stenta organization(s): Farmier
oily volunteering organization(s): Cactus Blossom IT Services Limited
catch organization(s): Third and Grove
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.