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

Choose whether note is resolvable

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
gitlab, lua, neovim
领域
api, tooling

调研方向

从 require("gitlab").create_note() 和笔记弹窗入手,然后比较直接笔记与之后发布的草稿笔记。检查 go-gitlab 是否支持选择评论或线程,以及公开内部标志。完成标准是弹窗可以选择所请求的笔记类型,并且生成的笔记与 GitLab 的行为一致。

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

描述

feature request

Feature Description

While working on #417, I've noticed that notes in gitlab.nvim are created as resolvable (i.e., as threads) when they are created directly with require("gitlab").create_note(), but as non-resolvable when they are first created as a draft note and then published. While I don't think this causes any real problems to users, it may be a little confusing why some notes need to be resolved and some not.

To match the behaviour of Gitlab online, (and if this is supported by go-gitlab) users should have the possibility of choosing whether they create a note as a non-resolvable comment or a thread. This could be implemented as another field in the note popup next to "Draft", something like "Type" with the values "Comment" and "Thread".

I've also just noticed, that Gitlab also allows creating "Internal notes". gitlab.nvim should probably at least show the internal flag on the note, ideally, also enable users to create internal notes (that could be another field in the note popup).

主要语言
Lua
星标
402
派生
64
平均合并
7 小时 17 分钟
30 天内合并 PR
4

环境准备

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

从这里开始

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

harrisoncramer/gitlab.nvim 的其他 Issue

查看 harrisoncramer/gitlab.nvim 的全部 Issue

相似的 Issue

更多 Lua Issue

把新 issue 发到你的邮箱

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