Contribution records
Contributors

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

Give credit to everyone
mfernea mfernea organization(s): AmeXio Fuse
shkiper shkiper volunteering
andriyun andreyun volunteering organization(s): Bellcom, Drupal Ukraine Community customer(s): Drupal Ukraine Community
zaporylie zaporylie organization(s): Ny Media AS
martin107 martin107
xjm xjm organization(s): xjm
osman osman volunteering
quietone quietone volunteering organization(s): PreviousNext
alexpott alexpott organization(s): Acro Commerce, Thunder
daffie daffie organization(s): Finalist
larowlan larowlan organization(s): Acquia
longwave longwave organization(s): Full Fat Things customer(s): Acquia
smustgrave smustgrave organization(s): Mobomo
spokje Spokje volunteering
borisson_ borisson_ organization(s): Calibrate customer(s): Acerta
nod_ nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
jannakha jannakha organization(s): Tomato Elephant Studio
ioana apetri ioanaa20 volunteering
kul.pratap kulpratap2002 organization(s): Innoraft customer(s): Drupal India Association
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.