Issue
Contribution records
Contributors

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

Give credit to everyone
bdragon
joachim
xmacinfo organization(s): xMac info
jcnventura organization(s): Mearra (formerly known as Wunder)
lauriii volunteering organization(s): Druid
Bojhan volunteering
deepakkumar14 volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
heykarthikwithu volunteering organization(s): Friday Media Group, Material
ranjith_kumar_k_u organization(s): Zyxware Technologies
guilhermevp organization(s): CI&T
quietone volunteering
vikashsoni volunteering organization(s): Zyxware Technologies
dharmeshmertwal volunteering organization(s): Material
avpaderno volunteering
cilefen
rajandro volunteering organization(s): Material customer(s): Drupal India Association
smustgrave organization(s): Mobomo
Tor Arne Thune
devin carlson
Buoro.Angelo organization(s): Azri Solutions
daniel.nitsche organization(s): Modules in Depth
sonam.chaturvedi organization(s): QED42 customer(s): Drupal India Association
pooja saraah organization(s): Material customer(s): Drupal India Association
jonbob
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.