Issue
Contribution records
Contributors

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

Give credit to everyone
hctom organization(s): undpaul
spokje organization(s): Annertech
eelkeblok organization(s): One Shoe
cilefen organization(s): Institute for Advanced Study
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
xjm
crash_springfield
wells volunteering organization(s): Cascade PBS
shaal volunteering
lauriii organization(s): Acquia
vladimiraus organization(s): Tomato Elephant Studio
mikemadison organization(s): Acquia
phenaproxima organization(s): Acquia
pdenooijer customer(s): RTL Nieuws
jeromewiley
a.dmitriiev volunteering organization(s): 1xINTERNET
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.