coding-blocks / coding-blocks/codingblocks.com1
Action required: Greenkeeper could not be activated 🚨
- 主要語言
- HTML
- 星號
- 58
- 分支
- 168
- PR 合併指標
- 30 天內沒有已合併 PR
描述
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a [commit status](https://help.github.com/articles/about-statuses/) is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the [`greenkeeper/initial`](https://github.com/coding-blocks/codingblocks.com/commits/greenkeeper/initial) branch, it’s possible that you don’t have CI set up yet. We recommend using [Travis CI](https://travis-ci.org), but Greenkeeper will work with every other CI service as well.
If you _have_ already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with `greenkeeper/`.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the `greenkeeper/initial` branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s __settings__ page, under __Installed GitHub Apps__.
貢獻指南
這個儲存庫沒有索引到貢獻指南
研究方向
檢查儲存庫的 CI 設定,以及它是否會在 greenkeeper/initial 分支上回報提交狀態。檢視 Installed GitHub Apps 下的儲存庫或組織設定,然後確認 CI 涵蓋新的 greenkeeper/* 分支。完成的標準是 Greenkeeper 收到 CI 狀態,且其初始提取要求可以重新觸發。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- github
- 領域
- ci-cd, devops
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 30/100