Repositories exclusion not working for empty repos
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- github-actions, javascript
- 领域
- devops
调研方向
从 deployment-settings.yml 中的排除配置开始,跟踪 GitHub Action 的设置强制执行入口直到 branch-protection 请求。使用一个被排除的空仓库重现问题,然后验证被排除的仓库会在任何强制执行调用之前被跳过,而未被排除的仓库仍会强制执行设置。
由索引模型根据 Issue 内容生成。
描述
Problem Description
I have this deployment-settings.yml:
restrictedRepos:
exclude:
- repo-A
- repo-B
- myrepo
Settings are NOT enforced on myrepo as expected, but such enforcement is triggered on both repo-A and repo-B. Such enforcement fails cause repo-A and repo-B are still empty and an error is thrown.
What is actually happening
The settings enforcement is triggered even if repository is listed among the excluded ones.
What is the expected behavior
That the excluded repositories are actually excluded by any kind of attempt of settings enforcement.
Error output, if available
Error applying branch protection.
{
"name":"HttpError",
"status":404,
"data": {
"message":"Branch not found",
"documentation_url":"https://docs.github.com/rest/branches/branch-protection#update-branch-protection",
"status":"404"
}
}
Such error is totally fair cause the repos are effectively empty. But why does it matter since the repo should be excluded? It seems such exclusion is ignored.
Context
Are you using the hosted instance of probot/settings or running your own?
My own, deployed via Github action as per documentation
If running your own instance, are you using it with github.com or GitHub Enterprise?
github.com
Version of probot/settings
probot/13.4.4
Version of GitHub Enterprise
- 主要语言
- JavaScript
- 星标
- 942
- 派生
- 238
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github-community-projects/safe-settings 的其他 Issue
-
Teams: teams with organization-role access show up as deletions可能已有人在做 @TovaBecker 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 83/100
github-community-projects/safe-settings#1144 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
github-community-projects/safe-settings#1143 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
github-community-projects/safe-settings#1135 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
github-community-projects/safe-settings#1134 ·
维护者通常 2 天内回复
-
environments: additive_plugins is ignored, undeclared environments are deleted可能已有人在做 @yaunj 于 12 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
github-community-projects/safe-settings#1133 ·
维护者通常 2 天内回复
查看 github-community-projects/safe-settings 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
cytoscape/cytoscape.js#3597 ·
维护者通常 5 天内回复
-
priority: low server testing
难度 1/5 1 小时以内 新手友好度 88/100
blamechris/chroxy#9277 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
sunososobro-hub/cloudball#191 ·
维护者通常 1 天内回复
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)未关闭
难度 2/5 1-3 小时 新手友好度 62/100
microsoft/playwright#44289 ·
维护者通常 1 天内回复
-
area:post effort:low enhancement P7 source:agent
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复