Repository navigation
GitHub Workflow: Clean up CI workflow to avoid redundant work. - #655
KimonHoffmann merged 6 commits into
Conversation
1c87679 to
429baf4
Compare
b7dbf21 to
4ba642c
Compare
|
@KimonHoffmann should we backport to 1.1 or focus only on main? if so, please add the required labels. |
We could, yes. I'll add the labels accordingly. |
4ba642c to
0b9c7bf
Compare
|
@KimonHoffmann DCO issues on some commits. |
Ah, yes thank you. Fixed. Please note that I didn't yet merge the PR, because we need to coordinate this with the required PR status checks, as you can see above where it claims that there are "6 [status checks] expected" that did not yet complete. The reason for this is that the jobs changed and the 6 checks refer to the old set of jobs. I'd propose we do this all at once as part of today's TSC meeting so that everyone can rebase their PRs accordingly. |
3ebef61 to
6517b52
Compare
|
@KimonHoffmann is this ready to be merged? |
|
Yes I'll merge it this week. |
Signed-off-by: Kimon Hoffmann <Kimon.Hoffmann@lawo.com>
Signed-off-by: Kimon Hoffmann <Kimon.Hoffmann@lawo.com>
…tectures. Signed-off-by: Kimon Hoffmann <Kimon.Hoffmann@lawo.com>
Signed-off-by: Kimon Hoffmann <Kimon.Hoffmann@lawo.com>
Signed-off-by: Kimon Hoffmann <Kimon.Hoffmann@lawo.com>
6517b52 to
8fa7fb5
Compare
Signed-off-by: Jonas Ohland <jonas.ohland@gmail.com>
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/v1.0
git worktree add -d .worktree/backport/655/-/release/v1.0 origin/release/v1.0
cd .worktree/backport/655/-/release/v1.0
git switch --create backport/655/-/release/v1.0
git cherry-pick -x 47595150a308c1efe24d7ba5009d1878905fb0d5 cf00f3bfcf5e5599b65dc13b1bc648677b8636a4 11529690bc18e725dc8105510f561d1e3f387536 b9531641d3a0253a10850640a246e98ea8ddc08c 8fa7fb5e5f58cce6e25b14b3df54bfdf7eabc3eb 784280bdeed1aaaa3bade31d61fb193752c738b2 |
|
Successfully created backport PR for |


Orthogonalize the CI workflow by separating out redundant steps that were previously lumped in with other variations.
Details
Backport requirements
None.
Beneficial to have on all active branches, so labels have been added accordingly.
Notes
Once this branch has been merged it is important to update the PR merge requirements & status checks for the newly structured CI steps (which is why this PR currently claims that 6 status checks are missing).