Contribution records
Contributors

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

Give credit to everyone
opensense vidhatanand organization(s): OpenSense Labs
cilefen cilefen
xjm xjm organization(s): Acquia
jaykandari JayKandari volunteering organization(s): QED42
daffie daffie
shashikant_chauhan shashikant volunteering organization(s): Iksula
hgunicamp hgunicamp organization(s): CI&T
brahmjeet789 brahmjeet789 volunteering organization(s): gai Technologies Pvt Ltd
sharique sharique volunteering
pk188 pk188 organization(s): OpenSense Labs
voleger voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB, Lemberg Solutions customer(s): Drupal Ukraine Community, GOLEMS GABB, Lemberg Solutions
mile23 Mile23 volunteering
andypost andypost volunteering organization(s): Skilld
catch catch organization(s): Third and Grove
gaurav.kapoor gaurav.kapoor organization(s): OpenSense Labs
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.