Contribution records
Draft
Contributors

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

Give credit to everyone
drupa11y marcus.morba
Fulgrim Fulgrim
derhasi derhasi
seanb seanB
killerpoke killerpoke
grienauer Grienauer
mrakosms mrakosms
ballester ballester
ipwa ipwa
miro_dietiker mirodietiker organization(s): MD Systems GmbH
drobnjak drobnjak organization(s): MD Systems GmbH
johnchque yongt9412 organization(s): MD Systems GmbH
pixelmord pixelmord organization(s): Mearra (formerly known as Wunder) customer(s): Hubert Burda Media
gmclelland gmclelland
zerolab zerolab organization(s): Torchbox
Artnetik Artnetik volunteering
mtodor mtodor organization(s): Thunder
anybody Anybody
strykaizer StryKaizer volunteering organization(s): ClicketyClick
pivica pivica organization(s): MD Systems GmbH
stborchert stborchert organization(s): undpaul
jive01 jive01
jwilson3 jwilson3 organization(s): Bluespark
berdir berdir organization(s): MD Systems GmbH
Stalski stalski
jeroen.b jeroen.b
chr.fritsch chr.fritsch organization(s): Thunder
rajab natshah RajabNatshah organization(s): Vardot
jepster_ jepSter
daniel.bosen daniel.bosen organization(s): Thunder
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.