Issue
Contribution records
Contributors

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

Give credit to everyone
brunodbo
RobW
ParisLiakos
mrfelton
Rob_Feature
Kazanir
damienmckenna
shaundychko
SebCorbin
rooby
cosmicdreams
gmclelland
slashrsm
azinck
chrisschaub
aaron
supradhan
bgilhome
drupal_was_my_past
drupa11y
StevenWill
fengtan
igorik
micbar
alison
mirabuck
camdarley
iwayman
dddbbb volunteering
bneil
meecect
jmuzz
delmarr
bradezone
heddn
blasthaus
klokie
mstrelan
izmeez
Leeteq
chiebert
partdigital
kevinquillen
PI_Ron
circuscowboy
afsch volunteering organization(s): CivicActions
firewaller
steinmb volunteering
fuzzy76
mikeskull
devin carlson
martins.bertins
dave reid volunteering
gintaras.r
danny englander
henrijs.seso
rob c
tom.camp organization(s): CivicActions
joseph.olstad
fox mulder
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.