Issue
Contribution records
Contributors

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

Give credit to everyone
dcam
cilefen
longwave volunteering organization(s): Full Fat Things
larowlan organization(s): PreviousNext
megachriz organization(s): WebCoo
xrayfish
attraktive
catch organization(s): Third and Grove
z3cka
itaran
chrissnyder organization(s): Phase2
ankithashetty volunteering organization(s): Specbee
sinn customer(s): European Commission and European Union Institutions, Agencies and Bodies
tasc
dinesh18 volunteering organization(s): Singapore Press Holdings
dydave organization(s): Code Enigma
allella volunteering
carma03 volunteering
marthinal organization(s): Bluespark
jwilson3
nod_ volunteering
rschwab organization(s): University of California
joelpittet organization(s): The University of British Columbia
tonypaulbarker organization(s): Annertech
shawn dearmond
matas.k
Git commit message
Commit types
  • 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

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.