Contribution records
Contributors

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

Give credit to everyone
dalin dalin organization(s): Advomatic customer(s): Stanford University, The Episcopal Church
froboy froboy organization(s): Palantir.net customer(s): American Medical Association
nikunjkotecha nikunjkotecha volunteering organization(s): QED42
grndlvl grndlvl organization(s): GollyGood Software customer(s): Zivtech
kalyansamanta kalyansamanta organization(s): Asentech LLC
cilefen cilefen volunteering
pancho pancho volunteering
laravz LaravZ volunteering customer(s): DICTU
harpreet16 harpreet16 organization(s): Material customer(s): Drupal India Association
paulocs paulocs organization(s): CI&T
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
alexpott alexpott organization(s): Acro Commerce, Thunder
spokje Spokje volunteering
longwave longwave organization(s): Full Fat Things
quietone quietone volunteering
tim.plunkett tim.plunkett organization(s): Acquia
manuel.adan adan volunteering
anil.gangwal gangwalanil organization(s): Publicis Sapient customer(s): Publicis Sapient
geek-merlin geek-merlin organization(s): MachbarMacher
raman.b ramanbatra1709 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.