Contribution records
Contributors

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

Give credit to everyone
djsagar djsagar organization(s): OpenSense Labs
cilefen cilefen
quietone quietone organization(s): PreviousNext
jvbrian jvbrian organization(s): SeeD EM
ahsannazir ehsann_95 organization(s): QED42
pinesso Pinesso organization(s): ImageX customer(s): ImageX
mandymeng mandymeng
nod_ nod_ volunteering organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
anjaliprasannan AnjaliPrasannan volunteering organization(s): QED42
danrod danrod volunteering organization(s): esinergia., OPTASY
saurav-drupal-dev saurav-drupal-dev volunteering organization(s): Material customer(s): Drupal India Association
divyansh.gupta divyansh.gupta volunteering 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.