Issue
Contribution records
Contributors

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

Give credit to everyone
trevorbradley
cilefen organization(s): Institute for Advanced Study
berdir
alexpott organization(s): Thunder
larowlan volunteering organization(s): PreviousNext
jibran volunteering
zenimagine
Metztli
indigoxela
mkolar organization(s): Ciklum Western Europe customer(s): BurdaForward
catch organization(s): Third and Grove
jppo
tjtj
Egmund
adminMN2023
tmanhollan
translector
johnpitcairn
johnvenpin volunteering
tmwagner
skin
efpapado organization(s): Ramsalt Lab
Mitch5713
geerlingguy organization(s): Acquia
balintbrews
jcmartinez volunteering
sozkara volunteering
esod organization(s): Memorial Sloan Kettering Cancer Center
seanb organization(s): Acquia
allupaku
webdrips
bajah1701 volunteering
kfritsche organization(s): bio.logis Genetic Information Management GmbH
hchonov organization(s): bio.logis Genetic Information Management GmbH
saparker
mkaand
sfdrummer
dropa
jens peter
tim.plunkett organization(s): Acquia
Peter Buchanan volunteering
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.