• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In
Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.
New Repo Setting:
INCLUDE COVERAGE % WITH WARNINGS ABOUT DRIFTED BUILDS?

Enabling this setting will include a (potentially inaccurate) coverage % with warning messages in status updates for drifted builds.

Adjust setting

go-zoox / connect / 34596121665
34%
master: 36%

Build:
Build:
LAST BUILD BRANCH: feat/permissions-in-connect-token
DEFAULT BRANCH: master
Ran 11 Sep 2026 11:54AM UTC
Jobs 1
Files 61
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Sep 2026 11:42AM UTC coverage: 33.502% (+33.5%) from 0.0%
34596121665

Pull #24

github

whatwewant
feat(connect-token): carry user permissions inside X-Connect-Token

- user.Encode/Decode: sign the permissions claim too, upstream services so far had no
  way to resolve authorization from the token itself
- router: fill the permissions before signing the token in every mode (routes with a
  backend secret key, upstream mode, frontend + backend mode); a lookup failure is
  logged and leaves permissions empty, which upstream services treat as deny by default
- router: keep the permissions answered by the user service, the permissions service is
  only asked when the user service did not provide any
- tests: claim round trip, permissions injected into the upstream header, user service
  permissions not being replaced
Pull Request #24: feat: permissions in connect token

413 of 529 new or added lines in 24 files covered. (78.07%)

1127 of 3364 relevant lines covered (33.5%)

5.03 hits per line

Uncovered Changes

Lines Coverage ∆ File
20
64.29
app/admin/bootstrap/bootstrap.go
12
64.71
app/admin/api/login.go
12
81.82
app/admin/repository/rbac_repo.go
12
82.35
app/config/admin.go
9
25.0
app/admin/api/user.go
9
76.92
app/admin/static/embed.go
8
65.11
65.11% app/router/router.go
7
30.0
app/admin/api/users.go
6
33.33
app/admin/api/app.go
6
33.33
app/admin/api/menus.go
6
33.33
app/admin/api/permissions.go
6
51.46
51.46% app/app.go
2
60.96
60.96% app/config/defaults.go
1
94.12
app/admin/service/auth.go
Jobs
ID Job ID Ran Files Coverage
1 34596121665.1 11 Sep 2026 11:54AM UTC 61
33.5
GitHub Action Run
Source Files on build 34596121665
  • Tree
  • List 61
  • Changed 27
  • Source Changed 0
  • Coverage Changed 27
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #24
  • PR Base - master (#25097553190)
  • Delete
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