Issue
Contribution records
Contributors

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

Give credit to everyone
mglaman organization(s): Acquia
nkoporec
uditrawat volunteering
attilatilman organization(s): Cheppers customer(s): GatherContent
jcnventura organization(s): 1xINTERNET
phenaproxima organization(s): Acquia
loopy1492
anybody organization(s): DROWL.de
heddn organization(s): MTech, LLC
taran2l organization(s): Lemberg Solutions
wxman
samlerner organization(s): CivicActions customer(s): Centers for Medicare and Medicaid Services
dave reid volunteering organization(s): Lullabot customer(s): Principal Financial Group
wim leers organization(s): Acquia
lisa.rae volunteering organization(s): Plan Left
rajab natshah organization(s): Vardot customer(s): Vardot
Sana.Neyazi
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.