Issue
Contribution records
Contributors

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

Give credit to everyone
tkoleary organization(s): Acquia
Crell organization(s): Upsun (formerly Platform.sh)
webchick organization(s): Acquia
larowlan organization(s): PreviousNext
yoroy organization(s): Roy Scholten
phenaproxima organization(s): Acquia
berdir organization(s): MD Systems GmbH
anavarre organization(s): Acquia
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
jamesdeee volunteering
sam152 volunteering organization(s): PreviousNext
alexpott volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
boaloysius volunteering organization(s): Google Summer of Code
andypost volunteering organization(s): Skilld
amateescu customer(s): Pfizer, Inc.
jofitz organization(s): ComputerMinds
lauriii volunteering
kmajzlik organization(s): Ciklum Western Europe customer(s): BurdaForward
tacituseu
Bojhan volunteering
mtodor organization(s): Thunder
plach customer(s): Acquia
sahil432
arthurg
gaurav.kapoor organization(s): OpenSense Labs
gábor hojtsy organization(s): Acquia
manuel garcia volunteering organization(s): Appnovation
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.