Issue
Contribution records
Contributors

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

Give credit to everyone
anishnirmal organization(s): UniMity Solutions Pvt Limited
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
dbjpanda
psend volunteering organization(s): Drudesk, Internetdevels
dpi volunteering
markdorison organization(s): Chromatic
droplet
xjm organization(s): Acquia
yannickoo organization(s): Mearra (formerly known as Wunder)
flodevelop
othermachines
rachel_norfolk organization(s): Open Development Ltd customer(s): Horizons Unlimited
GrandmaGlassesRopeMan organization(s): Acquia
imiksu organization(s): Mearra (formerly known as Wunder)
duaelfr volunteering organization(s): Happyculture
tedbow organization(s): Acquia
lauriii volunteering
cilefen
tom robert
wim leers organization(s): Acquia
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.