Contribution records
Contributors

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

Give credit to everyone
opensense vidhatanand organization(s): OpenSense Labs
pritam-osl pritamprasun organization(s): OpenSense Labs
jaykandari JayKandari volunteering organization(s): QED42
cilefen cilefen
hgunicamp hgunicamp organization(s): CI&T
sharique sharique volunteering
jeetendrakumar jeetendrakumar volunteering organization(s): HyTechPro.com
jacobsanford JacobSanford volunteering
voleger voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB, Lemberg Solutions customer(s): Drupal Ukraine Community, GOLEMS GABB, Lemberg Solutions
alexpott alexpott organization(s): Acro Commerce, Thunder
avpaderno avpaderno volunteering
andypost andypost volunteering organization(s): Skilld
borisson_ borisson_
mondrake mondrake volunteering
quietone quietone organization(s): PreviousNext
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.