Contribution records
Contributors

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

Give credit to everyone
slashrsm slashrsm organization(s): MD Systems GmbH
pguillard pguillard
seanb seanB
phenaproxima phenaproxima organization(s): Acquia
jonathanshaw jonathanjfshaw
yoroy yoroy organization(s): Roy Scholten
shashikant_chauhan shashikant volunteering organization(s): Iksula
berdir berdir organization(s): MD Systems GmbH
marcoscano marcoscano organization(s): Lullabot customer(s): Acquia
Bojhan bojhan volunteering
xjm xjm organization(s): Acquia
mtodor mtodor organization(s): Thunder
martin107 martin107 volunteering
johnwebdev johnwebdev
woprrr woprrr volunteering organization(s): NeoLynk
bdimaggio bdimaggio volunteering organization(s): Acquia
benjifisher benjifisher organization(s): Isovera
larowlan larowlan organization(s): PreviousNext
webchick webchick organization(s): Acquia
chr.fritsch chr.fritsch organization(s): Thunder
wim leers wimleers organization(s): Acquia
gábor hojtsy goba organization(s): Acquia
ivan berezhnov IvanBerezhnov volunteering organization(s): Drupal Ukraine Community customer(s): Levi9
samuel.mortenson samuel.mortenson organization(s): Acquia
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.