Issue
Contribution records
Contributors

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

Give credit to everyone
askibinski
anavarre
eelkeblok organization(s): Dutch Open Projects
penyaskito volunteering
berdir
timodwhit
miro_dietiker organization(s): MD Systems GmbH
blueminds
drasgardian
iantresman
chriscohen
karolus
ebeyrent
greggles
Jaesin
sitordance
pookmish
hswong3i
RedactedProfile
duaelfr volunteering organization(s): Happyculture
sk33lz organization(s): Zivtech
grndlvl
koppie organization(s): Pantheon
Internet volunteering
eloivaque
agoradesign
guntervs
imrancluster
jomarocas volunteering
awasson
webchick organization(s): Acquia
obaydmir volunteering
andypost volunteering organization(s): Skilld
michelle organization(s): Current
glynster
RKopacz
robmccreary
drupalfever volunteering
dave reid volunteering organization(s): Lullabot
kim.pepper
rakesh.gectcr volunteering
ed@vtinq.org volunteering
andrej galuf
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.