Issue
Contribution records
Contributors

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

Give credit to everyone
ransomweaver
osman volunteering
jwilson3 organization(s): Bluespark
sandorczettner
justkristin
piridium
mikeker volunteering
dpacassi organization(s): Liip customer(s): FREITAG lab. AG
nicola85
bygeoffthompson
sonamsingh organization(s): Innoraft
ewaters5
legolasbo organization(s): Deeson
caspervoogt
AlexanderPop
rcodina
tkogias volunteering
dieuwe organization(s): Sparks Interactive
austin_brian
sutharsan
tim.plunkett organization(s): Acquia
Denis Danielyan volunteering
hendrik.fuss
nvaken
marcel tuchek
geek-merlin organization(s): MachbarMacher
marc angles
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.