Issue
Contribution records
Contributors

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

Give credit to everyone
svendecabooter volunteering organization(s): Sven Decabooter
phenaproxima organization(s): Acquia
benjy organization(s): PreviousNext
mikeryan volunteering organization(s): Acquia, Virtuoso Performance
quietone volunteering
andypost volunteering organization(s): Skilld
xjm
neerajsingh organization(s): Cognizant Technology Solutions
deepakaryan1988 organization(s): Therefore
imiksu volunteering organization(s): Mearra (formerly known as Wunder)
heddn organization(s): Acro Commerce, MTech, LLC
yogeshmpawar organization(s): QED42
jofitz organization(s): ComputerMinds, jofitz
pk188 organization(s): OpenSense Labs
alexpott organization(s): Acro Commerce
catch organization(s): Third and Grove
imalabya organization(s): Specbee
Sonal.Sangale organization(s): Blisstering Solutions
Jānis Bebrītis organization(s): Mearra (formerly known as Wunder)
manuel garcia volunteering organization(s): Appnovation
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.