Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
DanZ
jswainst
aromka
svdhout
scottAtRoot802
electropop
multiplextor
deanochips
markocall
brightbold
hanskuiters
dawehner volunteering
leilyrken
mxwright
LiorFil
ricobanga
maxplus
curt2199
melissavdh
yannickoo
samtny
MVRider
yktdan
ferrangil
drago239
jeremymcminn
mikey_p
wismbuh
kenorb
henrikakselsen
JulienThomas
johnwards
hockey2112
pbuyle
zura_lanch
splitsplitsplit
reysharks
danyalejandro
seren10pity13
jkingsnorth
Leeteq
aranmandapcel
jpvosmeer
pkeyes
joelpittet
thommyboy
winstonchurchil99 volunteering
smitty
rlmumford volunteering
esolitos organization(s): Ramsalt Lab
damienmckenna organization(s): Current
JRZ-2
richard.french
andy.smith
Media Crumb
Patrick Nelson
cameron prince
gfaustin@unm.edu
das-peter
petr.hajek organization(s): Aira GROUP s.r.o.
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.