Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Clean up "Should be removed" fields

Open
  • Is something wrong?
#131 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
grpc
Domain
api, backend-api-design

Research direction

Start with pull request 121 and locate the fields carrying the "Should be removed" comments. Remove those comments and mark the corresponding fields as reserved; the work is done when the affected API definitions reflect both changes and the repository validation passes.

Written by the indexing model from the issue text.

Description

bug

In https://github.com/temporalio/api/pull/121 I added a few "Should be removed" comments to some fields. Remove them and mark them as reserved. Was not done in that PR to avoid doing any non-comments changes.

Dominant language
Go
Stars
133
Forks
101
Avg merge
2d 9h
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from temporalio/api

All issues in temporalio/api

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.