ci: Consolidate and cleanup workflows #1646
Conversation
cgwalters
commented
Sep 24, 2025
cgwalters
commented
- Having separate workflows made sharing build artifacts not really possible, and it just makes sense to consolidate
- Refactor shared parts into a little internal action
cgwalters
force-pushed
the
build-sys-even-more2
branch
2 times, most recently
from
fe009f7 to
f3ce17d
Compare
|
To merge this we'll need to force it to override the expected CI contexts. |
- Having separate workflows made sharing build artifacts not really possible, and it just makes sense to consolidate - Refactor shared parts into a little internal action Signed-off-by: Colin Walters <walters@verbum.org>
There was a problem hiding this comment.
Hi @cgwalters, Do we still need to run all those test when push to main?
There was a problem hiding this comment.
Probably not? I am not aware of anyone monitoring the actions that run post-merge (though of course we could start doing so).
What it would catch is semantic merge conflicts, but the more I think about it the more I feel we should go to merge queues.
There was a problem hiding this comment.
Yeah, we can move integration test into merge_queue trigger and keep the rest test in pull_request trigger?
There was a problem hiding this comment.
Do you think that should block this one?
There was a problem hiding this comment.
We do not need to run same test twice (pull_request and merge_queue).
We can land this PR first and make changes when we enable merge_queue.
There was a problem hiding this comment.
OK can you approve the PR please?
cgwalters
force-pushed
the
build-sys-even-more2
branch
from
f3ce17d to
47c2bd1
Compare
|
I've adjusted the required CI context names to match this PR. |
|
Note: This means all outstanding PRs will need to be rebased |
2 participants
