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

Migrate CircleCI account mode to “GitHub OAuth app”

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
停滞
技术栈
github
领域
ci-cd

调研方向

Start in the CircleCI web app Dashboard and inspect the project URL to confirm its current account mode. Review the existing .circleci/config.yml and the linked CircleCI GitHub Apps documentation, then migrate the account from GitHub OAuth app to GitHub App. Done means the project uses the GitHub App URL style and can support multiple configurations.

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

描述

enhancement

CircleCI seems to support having multiple YAML config files, which might be a way to break up our monolithic configuration into more manageable pieces:

Within CircleCI, a project can have one or more configurations, which are pipeline definitions. Configurations include, but are not limited to, a .circleci/config.yml file in your repository.

This is only supported in Github App mode, not in GitHub OAuth app mode, which we are currently using – see the top-level info box on the aforementioned support document:

GitHub authorization with CircleCI is changing. Starting August 2023 when you authorize your CircleCI account with GitHub, you may find this will be done through our GitHub App, rather than the GitHub OAuth app. You can see which account type you have by heading to the CircleCI web app, select Dashboard from the sidebar, and inspect the URL in your browser:

  • This style of URL indicates you authenticated with the GitHub App: https://app.circleci.com/pipelines/circleci/UTxCZDiJ9MLGLC8hR1ZDmg

  • This style of URL indicates you authenticated with the GitHub OAuth app: https://app.circleci.com/pipelines/github/<your GitHub username/organization name>

For more information about the differences, see the GitHub docs comparison page.

主要语言
Python
星标
3.5k
派生
293
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

tiny-pilot/tinypilot 的其他 Issue

查看 tiny-pilot/tinypilot 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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