Contribution records
Contributors

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

Give credit to everyone
dydave DYdave organization(s): Code Enigma
vishalkhode vishal.khode volunteering organization(s): Acquia
alvarodemendoza ADeMendoza volunteering
scott_earnest scott_earnest
ivnish ivnish
sgurlt sgurlt volunteering
somersoft somersoft
manishvaity manishvaity
abelpzl abelpzl volunteering
pick_d pick_d
avpaderno avpaderno volunteering
bnjmnm bnjmnm organization(s): Acquia
pminf pminf organization(s): Abgeordnetenwatch
adamps AdamPS organization(s): AlbanyWeb
will_frank will_frank volunteering
krakenbite KrakenBite
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.