Contribution records
Contributors

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

Give credit to everyone
ckrina ckrina organization(s): Lullabot
kunalkursija kunal.kursija organization(s): Axelerant
m4olivei m4olivei organization(s): Lullabot
sagarmohite0031 sagarmohite0031 organization(s): QED42 customer(s): Drupal India Association
berdir berdir organization(s): MD Systems GmbH
plopesc plopesc organization(s): Lullabot
lauriii lauriii organization(s): Acquia
finnsky finnsky organization(s): Skilld
nod_ nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
anjali rathod anjali15 organization(s): Axelerant customer(s): Drupal India Association
roshni upadhyay roshni-upadhyay
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.