Contribution records
Draft
Contributors

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

Give credit to everyone
kostyashupenko kostyashupenko organization(s): Skilld
ckrina ckrina organization(s): Lullabot
mherchel mherchel volunteering organization(s): Agileana
skaught SKAUGHT organization(s): OPTASY
sakthi_dev sakthi_dev organization(s): Specbee customer(s): Drupal India Association
catch catch organization(s): Third and Grove
mgifford mgifford organization(s): CivicActions
plopesc plopesc organization(s): Lullabot
bnjmnm bnjmnm organization(s): Acquia
kentr kentr volunteering
prashant.c Prashant.c volunteering organization(s): QED42 customer(s): QED42
nod_ nod_ organization(s): Très Bien Tech customer(s): Palantir.net, Vardot, OPTASY, OpenSense Labs
xjm xjm organization(s): Zoocha, xjm, QED42
gábor hojtsy goba organization(s): Acquia
lauriii lauriii organization(s): Acquia
ambient.impact Ambient.Impact volunteering
xmacinfo xmacinfo volunteering organization(s): xMac info
mortona2k mortona2k
dydave DYdave volunteering organization(s): Code Enigma
smustgrave smustgrave organization(s): Mobomo
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.