10000 chore: improve variable names of mocked users · coder/coder@60810b9 · GitHub

Address: [go: up one dir, main page]

Include Form Remove Scripts Session Cookies

Skip to content

Navigation Menu

Appearance settings

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

coder / coder Public

Notifications You must be signed in to change notification settings
Fork 943
Star 10.4k

Code
Issues 588
Pull requests 40
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

ci

chore: improve variable names of mocked users #38080

Sign in to view logs

Sign in to view logs

chore: improve variable names of mocked users

chore: improve variable names of mocked users #38080

Uh oh!

There was an error while loading. Please reload this page.

Summary
Jobs
- changes
- gen
- lint
- fmt
- test-go
- test-cli
- test-go-pg
- test-go-pg-16
- test-go-race
- test-go-race-pg
- test-go-tailnet-integration
- test-js
- test-e2e
- chromatic
- offlinedocs
- build-dylib
- sqlc-vet
- build
- required
- deploy
- deploy-wsproxies
- notify-slack-on-failure
Run details
- Usage
- Workflow file

Usage Workflow file

gen

succeeded May 7, 2025 in 4m 1s

Loading

Re-running jobs...

You can’t perform that action at this time.

0