Issue
Contribution records
Contributors

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

Give credit to everyone
David_Rothstein volunteering
pounard
twistor volunteering
anavarre organization(s): Acquia
matglas86
mustanggb
mikeytown2
omega8cc
btopro
fabianx volunteering organization(s): Tag1 Consulting, Inc.
damienmckenna organization(s): Current
cyberwolf organization(s): 2DotsTwice bvba customer(s): European Commission and European Union Institutions, Agencies and Bodies
geerlingguy organization(s): Acquia
ayesh
dillix
bojanz
megachriz volunteering organization(s): WebCoo
Crell organization(s): Upsun (formerly Platform.sh)
heddn organization(s): MTech, LLC
klausi organization(s): jobiqo - job board technology
Tharick
andypost volunteering organization(s): Skilld
cilefen volunteering
chrisgross
webservant316
eporama organization(s): Acquia
madri2
heyyo
freelylw
skaught volunteering
littletiger
ayalon
alesr
rahim123
stefan.r
greg.1.anderson organization(s): Pantheon
alan d.
jonathan.green
kc-drupal volunteering
joseph.olstad
hass
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.