kernelci / kernelci/kernelci-deploy

Add indicator that a PR has been included in the latest staging build

Open
#14 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
4
Forks
19
Avg merge
3d 9h
Merged PRs (30d)
3

Description

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.

Contributor guide

No contributing guide indexed for this repository

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.