Contribution records
Contributors

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

Give credit to everyone
hooroomoo hooroomoo organization(s): Acquia
poker10 poker10 organization(s): ActivIT s.r.o.
lauriii lauriii organization(s): Acquia
benjifisher benjifisher organization(s): Tag1 Consulting, Inc.
rkoller rkoller
simohell simohell organization(s): Druid
ckrina ckrina organization(s): Lullabot
quietone quietone volunteering
narendrar NarendraR volunteering organization(s): Acquia
srishtiiee srishti.bankar organization(s): Acquia
catch catch organization(s): Third and Grove
nod_ nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
nicxvan nicxvan organization(s): nLightened Development LLC
omkar.podey omkar.podey organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
kunal.sachdev kunal.sachdev organization(s): Acquia
gábor hojtsy goba organization(s): Acquia
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.