Issue
Contribution records
Contributors

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

Give credit to everyone
pp
cweagans
shenzhuxi
LordBobo
cilefen
danquah organization(s): Reload
boedah
holingpoon
jhedstrom
alexpott
smaz
willzyx
xjm organization(s): Acquia
jmolivas organization(s): JAKALA (formerly FFW)
kenorb
David_Rothstein volunteering
esod volunteering
andypost volunteering organization(s): Skilld
proofoftom volunteering
mikran organization(s): Mediamaisteri Oy
michael_wojcik volunteering organization(s): Current
pwolanin volunteering organization(s): SciShield
bserem organization(s): zehnplus
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
derheap volunteering
dsnopek
catch organization(s): Third and Grove
hchonov organization(s): bio.logis Genetic Information Management GmbH
fgm volunteering organization(s): OSInet
divined
greg.1.anderson
wim leers organization(s): Acquia
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.