Contribution records
Contributors

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

Give credit to everyone
merauluka merauluka organization(s): Current
labboy0276 labboy0276 organization(s): Tandem
berdir berdir organization(s): MD Systems GmbH
LaurensV LaurensV
martinpe martinpe
nicrodgers nicrodgers organization(s): Welsh Government
rferguson rferguson
chop chop
erichomanchuk erichomanchuk
grimreaper florenttorregrosa organization(s): Smile
Sarenc Sarenc
5n00py 5n00py volunteering
deviantintegral deviantintegral organization(s): Lullabot
vijaycs85 vijaycs85 volunteering organization(s): Lullabot, Solathat
skylord skylord
lupusgr3y mgp_novicell organization(s): Novicell
akbuje akbuje volunteering
jasonawant jwant organization(s): Nerdery
amateescu amateescu customer(s): Pfizer, Inc.
RmrJmrGrl RmrJmrGrl
lukas.fischer lukas.fischer
sunil s. i_love_drupal
nikolay borisov flesheater
Chris Charlton chrischarlton volunteering
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.