Issue
Contribution records
Contributors

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

Give credit to everyone
kostyashupenko organization(s): Skilld
KeyboardCowboy organization(s): Lullabot
skaught organization(s): OPTASY
ahsannazir organization(s): QED42
godotislate organization(s): Digital Polygon
ckrina organization(s): Lullabot
plopesc organization(s): Lullabot
catch organization(s): Third and Grove
quietone organization(s): PreviousNext
m4olivei organization(s): Lullabot
nod_ volunteering organization(s): Très Bien Tech customer(s): Liip, OPTASY, Palantir.net, Vardot
longwave organization(s): Full Fat Things
prashant.c volunteering organization(s): QED42 customer(s): QED42
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.