Contribution records
Contributors

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

Give credit to everyone
prudloff prudloff organization(s): Insite
cilefen cilefen
tobiasb tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen customer(s): publicplan GmbH
ilgnerfagundes ilgnerfagundes organization(s): CI&T
catch catch organization(s): Third and Grove
pasqualle pasqualle volunteering
ultimike ultimike organization(s): DrupalEasy
mullzk mullzk
binnythomas binny_zyxware organization(s): Axelerant customer(s): Drupal India Association
jurgenhaas jurgenhaas organization(s): LakeDrops
lostcarpark lostcarpark volunteering
guzmanb guzmanb
hexaki hexaki
rauch rauch
samuel_orhan samuel_orhan
nod_ nod_ volunteering
volkswagenchick volkswagenchick organization(s): The Linux Foundation
bramdriesen bramdriesen volunteering organization(s): Sopra Steria
longwave longwave organization(s): Full Fat Things
ronraney rraney
guiu.rocafort.ferrer guiu.rocafort.ferrer volunteering
maxime.rffd maxime.rffd
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.