Contribution records
Contributors

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

Give credit to everyone
markconroy MarkConroy volunteering organization(s): Annertech
David_Rothstein drothstein volunteering
ckrina ckrina volunteering
harsha012 harsha012 volunteering organization(s): Red Crackle
larowlan larowlan organization(s): PreviousNext
navneet0693 navneet0693 volunteering organization(s): QED42
brahmjeet789 brahmjeet789 volunteering organization(s): gai Technologies Pvt Ltd
punamshelke PunamShelke organization(s): UniMity Solutions Pvt Limited
yepa Mickael-Silvert organization(s): Happy Coding
sutharsan sutharsan organization(s): ronder
lauriii lauriii organization(s): Acquia
longwave longwave volunteering
spitzialist spitzialist volunteering organization(s): Unic
volkswagenchick volkswagenchick organization(s): Kanopi Studios
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
vsujeetkumar vsujeetkumar organization(s): Material customer(s): Drupal India Association
gauravvvv Gauravmahlawat organization(s): OpenSense Labs
gábor hojtsy goba organization(s): Acquia
eli-t Eli-T
rinku jacob 13 RinkuJacob13 organization(s): Zyxware Technologies
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.