Summary
Add a GitHub Actions workflow that runs Chelonian against a ROS workspace and publishes the generated analysis report as a static page.
Motivation
Chelonian already has strong value as a local CLI, but one of its most practical use cases is continuous visibility of a workspace's structure and findings.
If analysis and report publication can be automated in GitHub Actions, users would be able to:
- continuously inspect workspace/package dependencies
- share static report pages with a team
- review findings without requiring a local Chelonian setup
- use Chelonian as part of documentation / review / CI workflows
Scope
At this stage, this issue is intentionally broad and can start as a single tracking issue.
Implementation may require work in this repository and possibly in a separate repository depending on how reusable the workflow is intended to be.
Possible directions
- add a workflow template in this repository
- add a reusable workflow for other repositories
- support publishing to GitHub Pages
- support configurable target workspace paths and report output locations
- optionally support scheduled runs and/or runs on push
Notes
This is related to the existing sample-report publishing idea, but the goal here is broader: enabling workspace analysis/report publishing as a reusable workflow pattern, not only maintaining a single sample page.
Summary
Add a GitHub Actions workflow that runs Chelonian against a ROS workspace and publishes the generated analysis report as a static page.
Motivation
Chelonian already has strong value as a local CLI, but one of its most practical use cases is continuous visibility of a workspace's structure and findings.
If analysis and report publication can be automated in GitHub Actions, users would be able to:
Scope
At this stage, this issue is intentionally broad and can start as a single tracking issue.
Implementation may require work in this repository and possibly in a separate repository depending on how reusable the workflow is intended to be.
Possible directions
Notes
This is related to the existing sample-report publishing idea, but the goal here is broader: enabling workspace analysis/report publishing as a reusable workflow pattern, not only maintaining a single sample page.