Contribution records
Contributors

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

Give credit to everyone
chrisfromredfin chrisfromredfin
jhodgdon jhodgdon
luismagr luismagr volunteering organization(s): Front ID
ericg8645 ericg8645
ahoms ahoms volunteering
antongp antongp organization(s): ADCI Solutions
denns0r denns0r
josueValRob josueValRob volunteering
baronmunchowsen baronmunchowsen
Ante890 Ante890
pcambra pcambra
cilefen cilefen volunteering organization(s): Institute for Advanced Study
wturrell wturrell volunteering
webcultist webcultist
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
el7cosmos el7cosmos volunteering organization(s): Alterra
manningpete manningpete organization(s): American Medical Association
darvanen Darvanen
rooby rooby
wesleymusgrove wesleymusgrove
akupaka akupaka
joelpittet joelpittet volunteering
ressa ressa organization(s): Ardea
bdanin bdanin
fadehelix fadehelix
Tom Nelson Tom Nelson
gaurav.kapoor gaurav.kapoor
Koen Verheyen KoenVerheyen
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.