Issue
Contribution records
Contributors

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

Give credit to everyone
sylvainm organization(s): Axess Open Web Services
rocketeerbkw
joelstein
ckng organization(s): BaasBook, Classes.my
anybody organization(s): DROWL.de
heddn organization(s): Forum One, MTech, LLC
bogdog400 volunteering
nerdoc volunteering
culfin
garphy organization(s): ICI LA LUNE
jaypan organization(s): Jaypan
3dnathaniel
xtaz
wylbur volunteering
ronan
wizonesolutions volunteering
howdytom
shahidbscs
alh
3cwebdev
nancydru
wOOge
selinav
damienmckenna organization(s): Current
frank hh-germany
nagy.balint
kevin morse
alan d.
gchalker@princeton.edu
vincent wasswa
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.