Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jibran
fago organization(s): drunomics
klausi
andypost volunteering organization(s): Skilld
eclipsegc
daffie
jhedstrom organization(s): Phase2
benjy organization(s): PreviousNext
MerryHamster organization(s): Skilld customer(s): Skilld
basil_snowman volunteering customer(s): Skilld
vacho organization(s): Skilld
aleevas organization(s): Skilld
tr
quietone organization(s): PreviousNext
dpi organization(s): PreviousNext
michaellander organization(s): Elevated Third
jurgenhaas organization(s): LakeDrops customer(s): OPTASY
tim.plunkett organization(s): Acquia
kim.pepper
ravi.shankar organization(s): OpenSense Labs
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.