Work on Milestone -7 #8
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
…cs Verification, Release Automation ## Phase 2: CI/CD Pipeline - Add .github/workflows/ci.yml with Ruby matrix testing (3.0-3.3) - Add RuboCop lint check with .rubocop.yml configuration - Add Codecov integration for test coverage - Add VSCode and JetBrains plugin build/verify steps - Add docs verification CI step - Create .github/workflows/release.yml for simultaneous deployment - Remove legacy wasm-publish.yml (now integrated into release.yml) ## Phase 3: Editor Plugin Integration - Add editors/VERSION as single source of truth (v0.2.0) - Create scripts/sync-editor-versions.sh for version synchronization - Setup VSCode test framework with @vscode/test-electron + Mocha - Write VSCode plugin tests (extension.test.ts) - Setup JetBrains test framework with JUnit 5 - Write JetBrains plugin tests (TRubyFileTypeTest, TRubySettingsTest) - Create editors/CONTRIBUTING.md with plugin contribution guide ## Phase 4: Documentation Verification - Create DocsExampleExtractor for Markdown code block extraction - Create DocsExampleVerifier for compile/typecheck validation - Create DocsBadgeGenerator for coverage badges (JSON, SVG) - Create Rakefile with docs:verify, docs:badge, docs:list tasks ## Phase 5: Release Automation - Create COMMIT_CONVENTION.md with Conventional Commits guide - Create .releaserc.yml for semantic-release configuration - Configure automatic CHANGELOG generation
yhk1038
deleted the
claude/milestone-negative-seven-01JDk66SKedBEZwn7hJXKEWt
branch
yhk1038
added a commit
that referenced
this pull request
Dec 14, 2025
…cs Verification, Release Automation (#8) ## Phase 2: CI/CD Pipeline - Add .github/workflows/ci.yml with Ruby matrix testing (3.0-3.3) - Add RuboCop lint check with .rubocop.yml configuration - Add Codecov integration for test coverage - Add VSCode and JetBrains plugin build/verify steps - Add docs verification CI step - Create .github/workflows/release.yml for simultaneous deployment - Remove legacy wasm-publish.yml (now integrated into release.yml) ## Phase 3: Editor Plugin Integration - Add editors/VERSION as single source of truth (v0.2.0) - Create scripts/sync-editor-versions.sh for version synchronization - Setup VSCode test framework with @vscode/test-electron + Mocha - Write VSCode plugin tests (extension.test.ts) - Setup JetBrains test framework with JUnit 5 - Write JetBrains plugin tests (TRubyFileTypeTest, TRubySettingsTest) - Create editors/CONTRIBUTING.md with plugin contribution guide ## Phase 4: Documentation Verification - Create DocsExampleExtractor for Markdown code block extraction - Create DocsExampleVerifier for compile/typecheck validation - Create DocsBadgeGenerator for coverage badges (JSON, SVG) - Create Rakefile with docs:verify, docs:badge, docs:list tasks ## Phase 5: Release Automation - Create COMMIT_CONVENTION.md with Conventional Commits guide - Create .releaserc.yml for semantic-release configuration - Configure automatic CHANGELOG generation
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.
…cs Verification, Release Automation
Phase 2: CI/CD Pipeline
Phase 3: Editor Plugin Integration
Phase 4: Documentation Verification
Phase 5: Release Automation