Issue
Contribution records
Contributors

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

Give credit to everyone
rsslwa
cilefen volunteering
MWaters
longwave organization(s): Full Fat Things
catch organization(s): Third and Grove
zieder
mark_fullmer volunteering organization(s): University of Texas at Austin
capellic
joelpittet organization(s): The University of British Columbia
bkosborne organization(s): Princeton University
eaajithe
smustgrave organization(s): Mobomo
pappis
willids
arefen
douggreen organization(s): Peak Digital, LLC
subir_ghosh
matt_paz
trevorbradley
kreatil
xamount volunteering
nelo_drup
jmohino
johnrosswvsu organization(s): Promet Source
wmfinck
mogio_hh
reloxo95 volunteering
sergeimalyshev volunteering
djdevin organization(s): Purple
admirernepali volunteering
mibstar
aaronelborg
mabho volunteering organization(s): ImageX
nicoleannevella volunteering
m.stenta organization(s): Farmier
eduardo morales alberti volunteering organization(s): Metadrop
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.