Issue
Contribution records
Contributors

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

Give credit to everyone
tstoeckler volunteering
dawehner volunteering
okay19
cs_shadow
alexpott organization(s): Acro Commerce, Chapter Three (acquired by Kanopi Studios), Thunder
rashid_786 organization(s): SDG Corporation
cilefen
snehi volunteering organization(s): Publicis Sapient customer(s): Publicis Sapient
quietone volunteering
kostyashupenko organization(s): Skilld
faline organization(s): CI&T
joelpittet organization(s): The University of British Columbia
catch organization(s): Third and Grove
chi
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
mxr576 organization(s): Pronovix
berdir organization(s): MD Systems GmbH
bircher volunteering organization(s): Nuvole
bbrala volunteering organization(s): SWIS
smustgrave organization(s): Mobomo
godotislate volunteering
borisson_ organization(s): Calibrate customer(s): Acerta
krishnan.n
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.