Issue
Contribution records
Contributors

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

Give credit to everyone
xjm organization(s): Acquia
gapple volunteering
memtkmcc organization(s): Omega8.cc
schnitzel organization(s): amazee.io
matkeane
serundeputy organization(s): Tandem customer(s): Backdrop CMS
keithdoyle9
dlufkin
pick_d
progga volunteering
espurnes volunteering
heddn organization(s): MTech, LLC
jaesperanza volunteering
pancho volunteering
borisson_ volunteering organization(s): Calibrate
geofflaw
gbaudoin volunteering organization(s): Swissquote
spuky volunteering
megachriz organization(s): WebCoo
effulgentsia organization(s): Acquia
socketwench organization(s): TEN7
legovaer organization(s): Cegeka customer(s): VDAB
mfb
quietone organization(s): PreviousNext
andypost volunteering organization(s): Skilld
r4arnys
shane birley
wim leers
christopher james francis rodgers
drunken monkey volunteering
francisco sierra volunteering
gábor hojtsy organization(s): Acquia
greg boggs
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.