[ci] establish baseline CI/CD checks - #974
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Establishing baseline CI/CD checks
Summary
This PR establishes the initial CI/CD baseline for LMFlow with fork-safe GitHub Actions workflows, offline CPU tests, lint checks, package validation, and GitHub Pages deployment.
Motivation
Previously we lacked a reliable CPU-only test workflow and package build validation. Several tests also depended on local datasets, network access, GPUs, or optional inference backends, making them unsuitable for standard pull request checks.
The documentation workflow attempted to deploy on pull requests, which could fail for contributions from forks due to restricted token permissions.
Changes
CI
Test isolation
tests/.ToolInferencertests and use the active Python interpreter for code execution.Documentation
main.gh-pagesbranch deployment action with the official GitHub Pages artifact workflow.Packaging
requires_pythonsetup argument withpython_requires.Requires-Python >=3.9in the built wheel metadata.Validation
The following checks were run locally:
actionlint: passed26 passed, 3 skipped, 22 deselectedThe documentation build currently reports 211 pre-existing warnings. Warning cleanup and enabling warnings-as-errors are intentionally deferred to a separate PR.