Contribution records
Contributors

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

Give credit to everyone
bojanz bojanz organization(s): Centarro
lsolesen lsolesen
funkym funkym
spydmobile spydmobile
corbin corbin
vasike vasike
Poieo Poieo
Knud Knud
atolborg atolborg
mrpeanut MrPeanut
drupallerina drupallerina
discipolo discipolo
mglaman mglaman organization(s): Centarro
sovarn sovarn
martinaelena martinaelena
bisonbleu bisonbleu
khumbu Khumbu
fox_01 fox_01
alexmcl alexmcl
juc1 Juc1
jantoine antoinesolutions
adambinkowski adambinkowski
pslcbs pslcbs
torgospizza torgospizza
jordimateubesancon jordimateubesancon volunteering
RAWDESK RAWDESK
anybody Anybody
joelpittet joelpittet
7thkey 7thkey volunteering
lslinnet lslinnet organization(s): Adapt
danon1981 danon1981
jonne.freebase jonne
geek-merlin geek-merlin organization(s): Clever Systems, DruConsult, MachbarMacher
thomas kaisuka DrupalHunk volunteering
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.