Contribution records
Contributors

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

Give credit to everyone
Bevan bevan
BenK benk
nlambert nlambert
davegan davegan
TimelessDomain TimelessDomain
geekgirlweb gamerxgirl
wallbay1 wallbay1
pdolphin pdolphin
lynnmart881 lynnmart881
AlanAtLarge AlanAtLarge
yugongtian yugongtian
BenPoole BenPoole
keesee CorpX
likewhoa likewhoa
glottus Glottus
kreynen kreynen
Miczka Miczka
bryancasler animelion
jenlampton jenlampton
drewish drewish
aaron aaron
rogical rogical
RikiB RikiB
dark11star dark11star
harriszrashid harriszrashid
artatac artatac
webchick webchick
franzkewd franzkewd
hansrossel hansrossel
Yorgg Yorgg
tugis tugis
zeezhao zeezhao
alberto56 alberto56
porg porg
webadpro webadpro
yan yan
anavarre anavarre
mototribe mototribe
aathewise simpsda volunteering
XiaN Vizjereij XiaN
alex ua alexua
Sylvain Lasnier SylvainLasnier
andrea.cavattoni andrea.cavattoni
johnv johnv
drupalvino drupalvino
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.