kernelci / kernelci/kernelci-deploy
Add indicator that a PR has been included in the latest staging build
- 主要言語
- Python
- スター
- 4
- フォーク
- 19
- 平均マージ
- 3日 9時間
- マージ済み PR(30日)
- 3
説明
At the moment, as [documented](https://kernelci.org/docs/instances/staging/) the staging pipeline automatically goes through each relevant kerrnelci repository and tries to merge [valid](https://kernelci.org/docs/instances/staging/#github-pull-requests) pull requests into a staging.kernelci.org branch for each repository.
These branches are then used in a "staging" version of kernelci.org - staging.kernelci.org.
The process occurs every 8 hours and it works great.
However, when there are lots of PRs for the same repository there is always a chance that there may be a merge conflict. If this happens the branch/PR being merged will be ignored. When this happens there is no way for the user to know that their PR hasn't been picked up by staging in the GitHub GUI unless they look through the commit log.
The goal for this ticket is to add a visible way to determine whether a PR is part of the latest staging.kernelci.org build.
This could be done by adding a new `in-staging` label, or by adding a comment, or both, or some other method.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
Start with the staging pipeline documentation at kernelci.org/docs/instances/staging/ and its GitHub pull requests section. Trace how valid pull requests are merged into each staging.kernelci.org repository branch, including the merge-conflict path. Done means users can determine in GitHub whether a pull request is included in the latest staging build.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- python
- 領域
- devops
- issue の種類
- 機能追加
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100