Issue
Contribution records
Contributors

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

Give credit to everyone
attiks organization(s): Attiks
marvin_b8 volunteering organization(s): comm-press
berdir organization(s): MD Systems GmbH
heykarthikwithu volunteering organization(s): Valuebound
lokapujya organization(s): Babson College
aerozeppelin
catch organization(s): Tag1 Consulting, Inc.
mac_weber volunteering
dawehner volunteering
alozie
Prasun
sudhanshug volunteering organization(s): Google Summer of Code
oknate volunteering
karan_kural
pguillard
darvanen
larowlan organization(s): PreviousNext
mpp organization(s): District09 customer(s): District09
banoodle organization(s): Kanopi Studios
guldi
claudiu.cristea organization(s): Webikon
wim leers organization(s): Acquia
johan.s
stefan.korn organization(s): Stefan Korn - Webentwicklung
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.