Contribution records
Contributors

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

Give credit to everyone
sludwig sludwig
akhmirem akhmirem
aenw aenw
yhhh9 yhhh9
alveoten alveoten
perusio perusio
antiorario antiorario
miaoulafrite miaoulafrite
tomsm tomsm
ferrum ferrum
carusen carusen
mandreato mandreato
rukaya rukaya
RobertOak RobertOak
marktheshark marktheshark
carvalhar carvalhar
bartezz bartezz
zeip ZeiP
chefarov chefarov
polskikrol polskikrol
mattcasey mbcasey
infines infines
manxian manxian
bwinett bwinett
zany zany
8perezm 8perezm
derjochenmeyer derjochenmeyer
rondp rondp
armyofda12mnkeys armyofda12mnkeys
grabby Grabby
CodeChaser CodeChaser
pifagor pifagor87 organization(s): GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
kristen pol kepol
g.paluch gpaluch
dave reid davereid
marco.difresco marco.difresco
serkan.arikusu serkanarikusu
harry slaughter hlslaughter
monil-dupe monil-dupe
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.