nextcloud / nextcloud/integration_github
'Default access token' doesn't seem to allow link previews at all
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 55
- 派生
- 13
- 平均合并
- 8 天 9 小时
- 30 天内合并 PR
- 10
描述
Hi
I want to enable link previews in Nextcloud documents for Github issues that are in private repositories.
I don't wish for my Nextcloud users to connect their own Github accounts to their Nextcloud accounts via OAuth.
I created a personal access token (the 'beta' kind, with finely scoped Read-Only access to: code, discussions, issues, metadata, and pull requests
I added that PAT to the global administrative settings in Nextcloud under settings/admin/connected-accounts as the 'Default access token'.
I ticked the box 'Enable Github link previews'
I still get 'Github API error Not Found' widgets appear in my documents when I paste a link to a Github issue in a private repository that this Github user has access to. The widget wants me to go to my personal account settings in Nextcloud to configure Github access, but I thought the 'default' access token should take care of it.
What's the problem? Is it the beta 'fine-grained' PAT method? I don't want to use the Classic method because I don't want Nextcloud to have write access to private repos through this token.
Otherwise, what are the scopes required for the PAT to work, with the beta method?
Do I still have to set up an OAuth2.0 app even though my use case is limited to link previews?
I am running Nextcloud 25.0.8, Github integration app 1.0.15
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 settings/admin/connected-accounts 流程和“Enable Github link previews”设置开始,然后在 Nextcloud 25.0.8 和 GitHub integration app 1.0.15 上使用细粒度只读 token 重现 Not Found 响应。完成标准是确定默认 token 是否支持私有 issue 预览,确定所需的 scopes 或 OAuth 要求,并记录或修正该行为。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, javascript
- 领域
- api, backend
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100