Issue
Contribution records
Contributors

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

Give credit to everyone
rodrigoaguilera organization(s): Ymbra customer(s): Ymbra
dgtlmoon volunteering
abramm organization(s): DevBranch, Drupal Ukraine Community
smustgrave organization(s): Mobomo
bkosborne organization(s): Princeton University
feyp volunteering organization(s): werk21
mstrelan organization(s): PreviousNext customer(s): Service NSW
quietone organization(s): PreviousNext
pirvudoru volunteering
catch organization(s): Third and Grove
attheshow organization(s): Richland Library
acbramley organization(s): PreviousNext
sukr_s volunteering
nod_ organization(s): Très Bien Tech customer(s): Liip, OpenSense Labs, OPTASY, Palantir.net, Vardot
evaldas.uzkuras
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.