Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
volkswagenchick organization(s): Red Hat
pieriwww organization(s): Evolving Web
rachel_norfolk volunteering
chrisdarke
cindytwilliams organization(s): Kanopi Studios
crasx organization(s): Bounteous
ekl1773 volunteering
greggmarshall volunteering organization(s): Vendor-Tech, Inc. customer(s): ZenSource
markie organization(s): Kanopi Studios
mradcliffe organization(s): Kosada
scorbine organization(s): Bounteous
vonreyes organization(s): Drupal Association
darren oh organization(s): Cognizant Softvision customer(s): Estée Lauder Companies
kristen pol organization(s): QuantCDN, Salsa Digital
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.