Issue
Contribution records
Contributors

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

Give credit to everyone
nkschaefer
_vid
waverate
d0t101101
polynya
mgifford
hvalentim
Rob_Feature
bago
jelo
koppie
tommybyskovlund
awolfey
TDI007
jantoine volunteering
helmo organization(s): Initfour websolutions
mrharolda
welly organization(s): PreviousNext
kurtfoster
Yuri
mingsong volunteering
oadaeh volunteering organization(s): Hook 42 customer(s): Zicasso, Inc.
jday
vacilando volunteering
aitala
gargsuchi organization(s): Salsa Digital customer(s): govCMS (Australian Government Department of Finance)
paulvandenburg
pandaski
greg.harvey
james.williams organization(s): ComputerMinds
kristen pol organization(s): Hook 42
steven jones
hass
quadrexdev volunteering organization(s): DevBranch, Drupal Ukraine Community
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.