Issue
Contribution records
Contributors

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

Give credit to everyone
imiksu volunteering
cilefen
berdir organization(s): MD Systems GmbH
catch
basvredeling organization(s): Code Culture
hussainweb organization(s): Axelerant
dawehner volunteering organization(s): Tag1 Consulting, Inc.
heddn organization(s): MTech, LLC
fabpot
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
MattA
jibran volunteering
effulgentsia organization(s): Acquia
larowlan volunteering
davidwbarratt volunteering organization(s): Golf Channel
webchick organization(s): Acquia
damiankloip
benjy organization(s): CodeDrop
timhilliard organization(s): Acquia
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
fabianx volunteering
kgoel organization(s): Forum One
wim leers organization(s): Acquia
kim.pepper organization(s): PreviousNext
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.