• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

VolvoxLLC / volvox-bot / 25573236171

08 May 2026 06:44PM UTC coverage: 90.22% (+0.01%) from 90.208%
25573236171

push

github

web-flow
Improve welcome setup publishing (#612)

* Improve welcome panel publishing

* Rate limit welcome publish routes

* Log welcome API publish failures

* Stop storing auth method as welcome actor

* Validate welcome publish channels by guild

* Add dedicated role menu channel

* Clarify introduction mention variables

* Remove stale welcome panel messages on channel change

* Surface welcome publication persistence warnings

* Clarify safe edit truncation logging

* Guard welcome panels against split payloads

* Guard welcome status fetches by guild

* Encode welcome panel publish route type

* Restore mocked fetch in onboarding tests

* Document mirrored welcome panel types

* Document welcome publication constraints

* Add welcome publishing coverage

* Add welcome setup changeset

* Expand welcome publishing branch coverage

* Document welcome panel selector design

* Document welcome route rate limits for CodeQL

* Restore web coverage gate

* Fix welcome publication edge cases

* Fix welcome dashboard status handling

* Surface welcome publication persistence gaps

* Validate welcome publish payloads

* Tighten web coverage and utility tests

* Refine welcome publish feedback

* Cover welcome API proxy routes

* fix: address welcome publish review feedback

* fix: address welcome setup sonar findings

* fix: preserve welcome publication ids on failures

* test: reduce welcome publishing duplication

* fix: address welcome publish review feedback

* fix: surface welcome publish persistence warnings

* fix(web): surface persist-warning toast on successful welcome publish

When Discord publish succeeds but DB state save fails, the API returns
status='posted' with persistWarning=true and lastError set. Previously
the UI treated any posted result as pure success. Now we check for
persistWarning/lastError on posted responses and show an info toast
with the warning message instead of a bare success toast.

Adds getWelcomePublishWarningMessage helper (sing... (continued)

10228 of 11975 branches covered (85.41%)

Branch coverage included in aggregate %.

188 of 202 new or added lines in 9 files covered. (93.07%)

6 existing lines in 3 files now uncovered.

16044 of 17145 relevant lines covered (93.58%)

168.66 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

84.47
/src/modules/welcomeDynamicContext.js


Build SHA Not Found

The commit SHA "a0ff5c43d0d5563a50603bb2b407a07bb68f49b4" was not found in your repository, so the file cannot be loaded. This may be because you posted from a local development environment, or your CI created an ephemeral commit.

STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc