Contribution records
Contributors

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

Give credit to everyone
jelle_s jelles
smustgrave smustgrave organization(s): Mobomo
luenemann luenemam organization(s): FlexiFlow GmbH
taraskorpach taraskorpach volunteering organization(s): Drupal Ukraine Community
tlo405 tlo405
randalv RandalV volunteering
makbay makbay
kufliievskyi kufliievskyi organization(s): publicplan GmbH
neclimdul neclimdul organization(s): APQC
malcomio malcomio organization(s): Capgemini
flocondetoile flocondetoile organization(s): Flocon de toile
ultimike ultimike organization(s): DrupalEasy
flyke flyke
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
alexpott alexpott volunteering
catch catch organization(s): Third and Grove
khiminrm khiminrm organization(s): Centarro
aaronbauman aaronbauman organization(s): Message Agency
eugen zerr eugenz3rr organization(s): arocom GmbH customer(s): arocom GmbH
aaron.ferris aaron.ferris organization(s): Zoocha
alina.basarabeanu alinaBasa organization(s): CACI Digital Experience (formerly Cyber-Duck)
eduardo morales alberti EduardoMoralesAlberti volunteering organization(s): Metadrop
tarik.cipix tlaasri
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.