Issue
Contribution records
Contributors

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

Give credit to everyone
estoclet organization(s): Smile
leroux_david organization(s): Luminess
paul_serval
sassafrass
alyaj2a organization(s): SeeD EM
leducdubleuet
nikit
joelseguin
rjw volunteering
shivam_tiwari organization(s): Innoraft
sk_10 volunteering
aangel organization(s): Performant Labs
rolodmonkey organization(s): Bixal
lmoeni organization(s): IT.NRW
martygraphie organization(s): Ecedi
adrianm6254 organization(s): net2Community, Inc.
ankitjhakal volunteering organization(s): Axelerant
tonytheferg
solimanharkas organization(s): Factorial.io
anybody organization(s): DROWL.de
ressa organization(s): Ardea
dydave organization(s): Code Enigma
niharika.s
stephenplatz
yonas.legesse volunteering
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.