Contribution records
Contributors

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

Give credit to everyone
Bojhan bojhan volunteering
yoroy yoroy organization(s): Mearra (formerly known as Wunder)
lisarex lisarex
dawehner dereine volunteering
drupalshrek drupalshrek
xjm xjm organization(s): Acquia, xjm
sun sun
jerdavis jerdavis
tstoeckler tstoeckler
klonos klonos
royal121 royal121
odegard odegard
damiankloip damiankloip
tadityar tadityar
eidoscom eidoscom
lendude Lendude volunteering
nlisgo nlisgo
dajjen dajjen
disasm disasm organization(s): AppliedTrust
metzlerd metzlerd volunteering
b_man B_man organization(s): Drupal Association
ohthehugemanatee ohthehugemanatee volunteering
yesct YesCT
Maouna Maouna organization(s): bio.logis Genetic Information Management GmbH
zekvyrin zekvyrin
penyaskito penyaskito volunteering
catch catch
nod_ nod_ volunteering
quietone quietone organization(s): PreviousNext
tim.plunkett tim.plunkett organization(s): Acquia
gábor hojtsy goba organization(s): Acquia
hass hass
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.