Contribution records
Contributors

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

Give credit to everyone
jonnyhocks jonnyhocks organization(s): Welsh Government
brunodbo brunodbo organization(s): Textillia
bletch bletch
roaldnel roaldnel organization(s): Finalist
rahul17 rahul17 organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
leraa leraa organization(s): ICF
jaydarnell CopperBot organization(s): CivicActions customer(s): LINCS
vflirt vflirt
thatguy thatguy organization(s): Siili Solutions
zanematthew zanematthew
gwvoigt gwvoigt
Holka_a Holka_a volunteering
daneduijnkerke daneduijnkerke volunteering
deasly Deasly
3li Eli.Stone volunteering
defcon0 Defcon0
c_archer c_archer volunteering organization(s): Whisky Auctioneer
gaurav_manerkar gaurav_manerkar organization(s): EPAM
nicole.harnish nmacd85
ioana apetri ioanaa20 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.