Issue
Contribution records
Contributors

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

Give credit to everyone
xjm organization(s): Acquia
phenaproxima organization(s): Acquia
jeroent organization(s): iO
andrewmacpherson volunteering
bnjmnm organization(s): Acquia
lauriii organization(s): Acquia
seanb volunteering
oknate volunteering
webchick organization(s): Acquia
svettes organization(s): Acquia
effulgentsia organization(s): Acquia
dyannenova organization(s): Acquia
marcoscano volunteering organization(s): Lullabot
webflo organization(s): UEBERBIT GmbH
berdir organization(s): MD Systems GmbH
feyp volunteering organization(s): werk21
annagaz
cboyden organization(s): UC Berkeley Web Platform Services
peterx volunteering
rainbreaw volunteering
shaal volunteering organization(s): Palantir.net
pookmish
wim leers organization(s): Acquia
gábor hojtsy organization(s): Acquia
chr.fritsch organization(s): Thunder
samuel.mortenson
jan.stoeckler
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.