-
Notifications
You must be signed in to change notification settings - Fork 0
Add smartem-workspace CLI package #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
…ew workspace for local dev
Collaborator
Author
|
Initial implementation complete. Package structure and CLI commands working. |
14 tasks
- Create ADR-0011 documenting removal of python-copier-template - Update ADR-0002 status to 'Superseded by ADR-0011' - Update README.md ADR table with supersession note - Update WebUI navigation and index to include ADR-0011 - Add missing ADR-0010 (Shiki) to WebUI decisions index This documents the decision made in smartem-decisions commit f95b1de to remove copier-template scaffolding and manage tooling directly.
Two fixes for Claude Code skill setup: 1. Update skill paths in bundled config (repos.json) - Add claude-code/ prefix to all skill paths - Before: shared/skills/database-admin - After: claude-code/shared/skills/database-admin - Fixes skill discovery during workspace initialization 2. Fix symlink creation in claude.py - Use os.symlink() with absolute paths instead of Path.symlink_to() - Path.symlink_to() was creating relative symlinks that resolved incorrectly - Ensures skills are accessible from .claude/skills/ directory Tested with wheel installation via uvx. All skills now symlink correctly and are accessible during workspace initialization. Resolves skill symlinking issues reported in testing.
Collaborator
Author
|
Local testing complete. Fixed skill symlink paths. 16/16 tests passing. |
… PyPI release Add complete documentation suite and GitHub Actions workflow for publishing smartem-workspace to PyPI: Documentation: - User guide (docs/how-to/setup-smartem-workspace.md) - 600+ lines Comprehensive guide for end users covering installation, presets, configuration options, troubleshooting, and post-setup steps - Developer guide (packages/smartem-workspace/docs/developer-guide.md) - 3000+ lines In-depth technical documentation covering architecture, package structure, core components, configuration system, development setup, testing strategy, CI/CD pipeline, contributing guidelines, and API reference - PyPI setup guide (packages/smartem-workspace/docs/pypi-setup.md) - 800+ lines Step-by-step instructions for maintainers to set up PyPI accounts, generate API tokens, configure GitHub Secrets, and handle token rotation with security best practices CI/CD Infrastructure: - GitHub Actions workflow (.github/workflows/publish-smartem-workspace.yml) 6 jobs: test, lint, build, version-bump, publish-testpypi, publish-pypi Features: - Change detection (only runs on package changes) - Automated version bumping with commitizen - TestPyPI publish on main branch pushes - PyPI publish on release tags (smartem-workspace-v*) - Codecov integration for coverage reporting - Package metadata validation README Updates: - Enhanced package README with PyPI badges, documentation links, and development instructions - Updated root README with smartem-workspace quick start section Ready for PyPI publication once organizational PyPI account is created and tokens are configured in GitHub Secrets. Completes documentation and CI/CD setup for PR #17.
Remove test coverage reporting - not meaningful for this type of CLI tooling. Tests still run in CI, just without coverage metrics.
Collaborator
Author
|
Updated CI workflow to use PyPI Trusted Publishers (OIDC) instead of API tokens. Removed TestPyPI and auto-bump jobs. Release process: create |
Move documentation from packages/smartem-workspace/docs/ to root docs/: - developer-guide.md -> docs/explanations/smartem-workspace-developer-guide.md - pypi-setup.md -> docs/how-to/publish-smartem-workspace-to-pypi.md Update all references in package README to point to proper locations. All documentation should live in the root docs/ directory, not scattered across package subdirectories.
vredchenko
added a commit
that referenced
this pull request
Jan 8, 2026
… PyPI release Add complete documentation suite and GitHub Actions workflow for publishing smartem-workspace to PyPI: Documentation: - User guide (docs/how-to/setup-smartem-workspace.md) - 600+ lines Comprehensive guide for end users covering installation, presets, configuration options, troubleshooting, and post-setup steps - Developer guide (packages/smartem-workspace/docs/developer-guide.md) - 3000+ lines In-depth technical documentation covering architecture, package structure, core components, configuration system, development setup, testing strategy, CI/CD pipeline, contributing guidelines, and API reference - PyPI setup guide (packages/smartem-workspace/docs/pypi-setup.md) - 800+ lines Step-by-step instructions for maintainers to set up PyPI accounts, generate API tokens, configure GitHub Secrets, and handle token rotation with security best practices CI/CD Infrastructure: - GitHub Actions workflow (.github/workflows/publish-smartem-workspace.yml) 6 jobs: test, lint, build, version-bump, publish-testpypi, publish-pypi Features: - Change detection (only runs on package changes) - Automated version bumping with commitizen - TestPyPI publish on main branch pushes - PyPI publish on release tags (smartem-workspace-v*) - Codecov integration for coverage reporting - Package metadata validation README Updates: - Enhanced package README with PyPI badges, documentation links, and development instructions - Updated root README with smartem-workspace quick start section Ready for PyPI publication once organizational PyPI account is created and tokens are configured in GitHub Secrets. Completes documentation and CI/CD setup for PR #17.
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.
Closes #16
Adds
smartem-workspace, a CLI tool to bootstrap SmartEM multi-repo workspaces.Changes
New package:
packages/smartem-workspace/init,sync,status,addminimal,smartem-core,full,aria-referenceCI/CD:
.github/workflows/publish-smartem-workspace.ymlsmartem-workspace-v*)Documentation
docs/how-to/setup-smartem-workspace.md- User guidedocs/how-to/publish-smartem-workspace-to-pypi.md- Release processdocs/explanations/smartem-workspace-developer-guide.md- Developer docsUsage
Pre-merge requirement
PyPI Trusted Publisher must be configured at https://pypi.org/manage/account/publishing/:
DiamondLightSourcesmartem-devtoolspublish-smartem-workspace.ymlpypi