Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): Red Hat
renatog renatog organization(s): CI&T
chrisdarke ChrisDarke organization(s): MindAtomic
crasx crasx volunteering organization(s): Bounteous
ekl1773 ekl1773 volunteering
greggmarshall greggmarshall organization(s): Vendor-Tech, Inc.
mradcliffe mradcliffe organization(s): Kosada
rachel_norfolk rachel_norfolk volunteering
vonreyes vonreyes organization(s): Drupal Association
cecilialevy CeciliaLevy
alison alison volunteering
cindytwilliams cindytwilliams organization(s): Kanopi Studios
dangur dangur
leslieg lglynn2299 organization(s): Redfin Solutions, LLC
markie markie
realityloop realityloop volunteering
sugaroverflow sugaroverflow
ptkoroma ptkoroma
amarshall-1 amarshall-1
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.