Contribution records
Contributors

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

Give credit to everyone
cpliakas cpliakas
PatchRanger Staratel
nod_ nod_
haggins haggins
chgasparoto chgasparoto volunteering organization(s): CI&T
nancydru nancyw
jonmcl JonMcL
dunebl dunebaud
szeidler szeidler organization(s): Ramsalt Lab
wells wells organization(s): Cascade PBS
alexpott alexpott volunteering organization(s): Acro Commerce, Thunder
lendude Lendude volunteering organization(s): iO
idebr idebr organization(s): iO
matroskeen Matroskeen organization(s): DevBranch, Drupal Ukraine Community, Evolving Web
larowlan larowlan organization(s): PreviousNext
dww dww organization(s): TEN7
jibran jibran volunteering
catch catch organization(s): Third and Grove
ben kuper benkuper
shiraz dindar Shiraz
amar.deokar amar.deokar
sukanya.ramakrishnan sukanya.ramakrishnan organization(s): Workday, Inc.
mogtofu33 mogtofu33
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.