Remove @ts-expect-error on custom properties API once octokit types are updated
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start by checking the upstream Octokit discussion linked in the issue to confirm that custom-properties endpoint types are available. Then inspect the three suppressed calls in src/server/repos/controller.ts, remove the @ts-expect-error comments, and verify that the TypeScript checks pass without them.
Written by the indexing model from the issue text.
Description
Context
In src/server/repos/controller.ts, octokit.rest.repos.getCustomPropertiesValues() and octokit.rest.orgs.getAllCustomProperties() / octokit.rest.orgs.createOrUpdateCustomProperty() are currently suppressed with @ts-expect-error because @octokit/plugin-rest-endpoint-methods (bundled in octokit v5) does not yet include type definitions for these endpoints. (introduced in PR #484
The endpoints exist in the GitHub API and work correctly at runtime — the suppression is purely
a types gap.
What needs to happen
Once the octokit upstream types are updated to include the custom properties endpoints, remove
the @ts-expect-error comments in src/server/repos/controller.ts.
Upstream tracking
- Dominant language
- TypeScript
- Stars
- 203
- Forks
- 42
- Avg merge
- 1h 15m
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github-community-projects/private-mirrors
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github-community-projects/private-mirrors#525 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/private-mirrors#524 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-2 days Newbie friendliness 68/100
github-community-projects/private-mirrors#449 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github-community-projects/private-mirrors#481 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
github-community-projects/private-mirrors#476 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in github-community-projects/private-mirrors
Similar issues
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
blamechris/chroxy#9272 ·
Maintainers usually reply within 1 day
-
no-repo-link tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 66/100
BraveOPotato/NoSignups#2458 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
drmrd/vernacular#1061 ·
Maintainers usually reply within 1 day