Issue
Contribution records
Contributors

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

Give credit to everyone
xjm organization(s): Acquia
JeremyFrench
sun
chx
cweagans
dcam
tanmayk
esoteric1
babruix
barnettech
webmozart
lendude volunteering organization(s): Dx Experts, Noctilaris
heddn
ceardach
IRuslan volunteering organization(s): DrupalJedi
nickdickinsonwilde
swentel
cilefen
gnuget volunteering
blazey volunteering
lomasr organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
suresh_ewall volunteering
dan2k3k4 organization(s): Amazee Labs
tstoeckler organization(s): bio.logis Genetic Information Management GmbH
catch organization(s): Third and Grove
tameeshb organization(s): Google Summer of Code
mkalkbrenner organization(s): bio.logis Genetic Information Management GmbH
sk33lz organization(s): Zivtech
hongpong volunteering organization(s): kor group
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
bapi_22 organization(s): Cybage Software Pvt Ltd.
andypost volunteering organization(s): Skilld
damien tournoud
tim.plunkett
star-szr
jp.stacey organization(s): Magnetic Phield
himanshu-dixit volunteering
Pavan B S organization(s): Valuebound
manuel garcia volunteering organization(s): Appnovation
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.