Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
akshay_d organization(s): Specbee customer(s): Drupal India Association
dasjo volunteering organization(s): Liip
teknocat
nessunluogo
kuhikar volunteering
ocastle organization(s): Full Bundle
mvdve
onfire84 organization(s): erdfisch
flyke
sorlov organization(s): Skilld
KondratievaS organization(s): Skilld
tormi organization(s): Mearra (formerly known as Wunder)
andypost volunteering organization(s): Skilld
anruether organization(s): Geeks4Change
delta
justachris organization(s): Bounteous
nitesh sethia volunteering organization(s): Digital Polygon
a.sotirov organization(s): JAKALA (formerly FFW)
tim-diels organization(s): Calibrate
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.