Issue
Contribution records
Contributors

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

Give credit to everyone
aspilicious
duwid organization(s): keytec GmbH & Co. KG
tonytheferg
rade organization(s): Mearra (formerly known as Wunder)
upchuk organization(s): European Commission and European Union Institutions, Agencies and Bodies, WEBOMELETTE
joevagyok customer(s): European Commission and European Union Institutions, Agencies and Bodies
liquidcms
jurgenhaas organization(s): LakeDrops
rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc.
stijndmd
lpeabody volunteering organization(s): Digital Polygon
thejimbirch organization(s): Kanopi Studios
ieguskiza organization(s): NTT DATA customer(s): European Commission and European Union Institutions, Agencies and Bodies
chewie
heddn organization(s): MTech, LLC
hanoii
n.ghunaim
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.