Issue
Contribution records
Contributors

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

Give credit to everyone
rachel_norfolk organization(s): Open Development Ltd
BarisW volunteering organization(s): ronder
rivimey volunteering
ifrik
csg organization(s): Cheppers
martin107 volunteering
ok_lyndsey volunteering
andrewmacpherson volunteering organization(s): Annertech
bojanz organization(s): Centarro
xjm organization(s): Acquia
wturrell volunteering
yoroy organization(s): Roy Scholten
tstoeckler volunteering
prabhu9484 organization(s): gai Technologies Pvt Ltd
mpdonadio organization(s): DiD Agency
lauriii organization(s): Druid
benjifisher organization(s): Isovera
zerbash
murrow volunteering
mgifford organization(s): OpenConcept Consulting Inc.
brettwilson organization(s): Redfin Solutions, LLC
droplet
larowlan organization(s): PreviousNext
mondrake volunteering
sam152 volunteering organization(s): PreviousNext
john cook volunteering organization(s): Creode
gábor hojtsy organization(s): Acquia
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.