Create tags for all crates?

未关闭
#17 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
github, rust
领域
devtools

调研方向

Read the issue’s examples of crate names in issue titles and the existing aes label in the block-ciphers repository. Decide whether to create prefixed labels for crates across RustCrypto repositories and apply them to all open issues; done means the labeling convention and the issues to update are agreed and consistently handled.

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

描述

Right now we mostly use the pattern of naming issues as <crate name>: <issue description>. It works fine, but makes harder to filter and search issues about a certain crate. In some repositories we have tags for crates (e.g. in block-ciphers we have aes), but it's more of an exception.

I wonder if we should be more consistent here by creating a tag for each crate in our repositories, and mark all (open) issues with relevant tags. We also probably need to introduce a prefix for such tags.

We also use may the tags for PRs, but I think we should continue to use the naming pattern, since github tags are not represented in Git history.

主要语言
没有语言数据
星标
13
派生
4
平均合并
41 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

RustCrypto/meta 的其他 Issue

查看 RustCrypto/meta 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

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