Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
valthebald organization(s): Dropsolid
udhaya kumar volunteering organization(s): UniMity Solutions Pvt Limited
maddyt organization(s): Zoocha
robertoperuzzo organization(s): SparkFabrik
dan2k3k4 organization(s): amazee.io
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
b_sharpe organization(s): ImageX
nexusnovaz volunteering organization(s): Zoocha
kristen pol organization(s): Itty Bitty Byte, Salsa Digital
matthews volunteering organization(s): amazee.io, James Matthew Saunders LLC
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.