Issue
Contribution records
Contributors

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

Give credit to everyone
effulgentsia organization(s): Acquia
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
berdir organization(s): MD Systems GmbH
webchick organization(s): Acquia
fabianx organization(s): Tag1 Consulting, Inc. customer(s): Pac-12 Networks, Pantheon
markgifford
borisson_ volunteering
nick_vh organization(s): Dropsolid
bendev organization(s): WebstanZ
grayle volunteering
dtv_rb
anavarre organization(s): Acquia
fgm volunteering organization(s): OSInet
dpw
neclimdul
pounard
smccabe volunteering organization(s): Acro Commerce
bdragon organization(s): Tag1 Consulting, Inc. customer(s): Pac-12 Networks, Pantheon
gogowitsch volunteering organization(s): QuoData GmbH Quality & Statistics customer(s): ÖQUASTA
bryanmanalo volunteering
alexpott organization(s): Thunder
jibran volunteering organization(s): PreviousNext customer(s): Service NSW
catch organization(s): Third and Grove
dww volunteering
mpp volunteering organization(s): AmeXio Fuse customer(s): District09
mondrake volunteering
larowlan organization(s): PreviousNext
m4olivei organization(s): Lullabot customer(s): NBCUniversal
sdelbosc
wim leers organization(s): Acquia
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
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.