Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

An efficient way to check on if a thread is in the Trash

未关闭
  • 哪里不对？
#607 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
cli

调研方向

Start by reading the CLI commands and API client that handle threads, messages, and Trash searches. The issue does not name files or tests, so trace how the existing Trash search works and whether the API supports checking known IDs in batches. Done means adding a read-only way to check whether threads or messages are in Trash, ideally in batches, and verifying it against existing command tests.

由索引模型根据 Issue 内容生成。

描述

As far as I can tell right now, there's no way given a thread id to tell if the thread is in the Trash.

I've built a local tool for reviewing some emails, and when that tool says I've handled all the items from those emails, I want to be able to delete those emails. I need the tool not to show the ones I've already deleted. Today the tool searches the Trash by account & received year, paginates through the results, and matches against the threads or messages locally, which can be slow when the Trash is large.

If there were a read-only way to check the current state of known threads or messages, ideally in batches, that would be very helpful.

主要语言
Go
星标
420
派生
54
平均合并
1 天 1 小时
30 天内合并 PR
49

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

basecamp/hey-cli 的其他 Issue

查看 basecamp/hey-cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。