Issue
Contribution records
Contributors

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

Give credit to everyone
sharique volunteering organization(s): Acquia customer(s): Acquia
bbrala volunteering organization(s): SWIS
nod_ organization(s): Acquia
andypost volunteering organization(s): Skilld
gabesullice
mpp organization(s): AmeXio Fuse customer(s): District09
joachim volunteering organization(s): Factorial.io
brianperry organization(s): Pantheon
johnny5th organization(s): RBN Energy, LLC.
yogeshmpawar organization(s): Portage CyberTech
d34dman volunteering organization(s): Factorial.io
avpaderno volunteering
baddysonja organization(s): 1xINTERNET
alexpott organization(s): Acro Commerce, Thunder
lauriii organization(s): Acquia
larowlan organization(s): PreviousNext
benjifisher volunteering organization(s): FRUITION
casey volunteering organization(s): SWIS
catch organization(s): Third and Grove
davidwbarratt volunteering
quietone organization(s): PreviousNext
xjm volunteering
wim leers organization(s): Acquia
suresh prabhu parkala organization(s): Specbee
gábor hojtsy organization(s): Acquia
ravi.shankar organization(s): OpenSense Labs
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.