Contribution records
Contributors

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

Give credit to everyone
shaal shaal volunteering organization(s): Palantir.net
byrond byrond organization(s): Palantir.net customer(s): Northcentral Technical College
shimpy shimpygupta volunteering organization(s): UniMity Solutions Pvt Limited customer(s): Drupal India Association
lauriii lauriii organization(s): Acquia
rakhimandhania rakhimandhania volunteering
imalabya malabya organization(s): Specbee
harishst HarishST volunteering customer(s): Drupal India Association
yoroy yoroy organization(s): Roy Scholten
hardik_patel_12 Hardik_Patel_12 organization(s): QED42
samiullah samiullah organization(s): Salsa Digital
msuthars msuthars organization(s): QED42 customer(s): Drupal India Association
alexpott alexpott organization(s): Acro Commerce, Thunder
priyanka.sahni priyanka.sahni organization(s): Material customer(s): Drupal India Association
kristen pol kepol organization(s): Hook 42 customer(s): Hook 42
harika gujjula harikagujjula organization(s): Specbee customer(s): Drupal India Association
ravi.shankar ravi.shankar 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.