Contribution records
Contributors

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

Give credit to everyone
baluv3 baluv3 organization(s): Lullabot
kostyashupenko kostyashupenko organization(s): Skilld
ckrina ckrina organization(s): Lullabot
rkoller rkoller
amandeep123 amandeep_lnwebworks organization(s): LN Webworks Private Limited
m4olivei m4olivei organization(s): Lullabot
adwivedi008 adwivedi008 organization(s): OpenSense Labs customer(s): DrupalFit
finnsky finnsky organization(s): Skilld
ahsannazir ehsann_95 organization(s): QED42
xjm xjm organization(s): HeroDevs
patrickfgoddard thund3rbox organization(s): Miles
smustgrave smustgrave organization(s): Mobomo
plopesc plopesc organization(s): Lullabot
nod_ nod_ organization(s): Très Bien Tech customer(s): OPTASY, Palantir.net
kanchan bhogade Kanchan-Bhogade organization(s): QED42 customer(s): Drupal India Association
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.