Issue
Contribution records
Contributors

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

Give credit to everyone
aalamaki
wroxbox
afox
fullerja
PavanL
David_Rothstein
tregismoreira
jelo
rteijeiro
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
sutharsan
larowlan volunteering organization(s): PreviousNext customer(s): University of Technology, Sydney
jibran volunteering
richardbporter volunteering
Screenack volunteering organization(s): Duke University
nkraft volunteering
afinnarn organization(s): University of Colorado Boulder
isramv
fabianx volunteering organization(s): Tag1 Consulting, Inc.
darkodev
tanubansal organization(s): Salsa Digital
kasey_mk
amietpatial volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
quietone volunteering
ayushmishra206 organization(s): OpenSense Labs
nikolaat
mohit_aghera organization(s): QED42
mark_fullmer organization(s): University of Texas at Austin
justcaldwell volunteering
douggreen
wim leers organization(s): Acquia
rakesh.gectcr volunteering organization(s): Valuebound
jeff cardwell organization(s): University of Texas at Austin
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.