Skip to content

ci: add optional praxis main testing and known-issue label#326

Draft
leseb wants to merge 2 commits into
praxis-proxy:mainfrom
leseb:leseb/test-on-main
Draft

ci: add optional praxis main testing and known-issue label#326
leseb wants to merge 2 commits into
praxis-proxy:mainfrom
leseb:leseb/test-on-main

Conversation

@leseb

@leseb leseb commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds praxis_main workflow_dispatch input to Tests and Integration workflows to optionally build/test against praxis core main branch instead of the crates.io release (uses [patch.crates-io] overrides)
  • Adds praxis-known-issue PR label support: when applied, jobs use continue-on-error so transient praxis core failures don't block PRs
  • Adds patch-praxis / unpatch-praxis Makefile targets for local development against a sibling ../praxis checkout
  • Restores clone-praxis composite action with configurable ref input and adds new patch-praxis composite action

Test plan

  • Manually trigger Tests workflow with praxis_main: true on this branch
  • Apply praxis-known-issue label and verify jobs report green on failure
  • Run make patch-praxis locally with ../praxis present, verify build

leseb added 2 commits July 9, 2026 21:46
Add CI support for testing against praxis core main branch via
workflow_dispatch input, and a praxis-known-issue PR label that
allows jobs to pass despite failures from transient core issues.

Signed-off-by: Sébastien Han <seb@redhat.com>
@leseb

leseb commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

I'm opening this as a draft since i think it's valuable to test regularly against praxis main but would like inputs from other maintainers too - @franciscojavierarceo @aslakknutsen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant