Contribution records
Contributors

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

Give credit to everyone
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
klausi klausi organization(s): jobiqo - job board technology
martin107 martin107 volunteering
jofitz jofitz organization(s): ComputerMinds
jhedstrom jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
phenaproxima phenaproxima organization(s): Acquia
michielnugter michielnugter volunteering organization(s): Synetic
lendude Lendude volunteering organization(s): Dx Experts
mpdonadio matthew.donadio organization(s): DiD Agency
ApacheEx ApacheEx volunteering organization(s): Drupal Ukraine Community
jonathan1055 jonathan1055 volunteering
amateescu amateescu customer(s): Pfizer, Inc.
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.