Contribution records
Contributors

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

Give credit to everyone
pvbergen pvbergen organization(s): iqual AG
biancaradu27 biancaradu27 organization(s): Dream Production
isaacrc isaacrc organization(s): Digitalist
nsciacca nsciacca
lysenko LHVR organization(s): DevBranch, Drupal Ukraine Community
dieterholvoet DieterHolvoet organization(s): Minsky
bkosborne bkosborne organization(s): Princeton University
phjou stargayte
tlo405 tlo405
zhelmet zHelmet
seanb seanB
pixelwhip pixelwhip organization(s): Aten Design Group
scott_euser scotteuser volunteering organization(s): Soapbox
danflanagan8 danflanagan8 organization(s): Horizontal
tichris59 tichris59
gomez_in_the_south Gomez
andreastkdf andreastkdf volunteering organization(s): Soapbox
i-trokhanenko i-trokhanenko organization(s): CACI Digital Experience (formerly Cyber-Duck), Inclind Inc
arturs.v arturs.v volunteering
wouter waeytens WouterWaeytens
georgebrook georgebrook
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.