Repository navigation
chore: bring back the contributor history from dev-workspace-cli - #3
Merged
Merged
Conversation
…r handling - Added a new "coverage" script to package.json for test coverage reporting using c8. - Introduced tests for CLI behavior on prompt abortion and unexpected errors. - Enhanced command execution tests to wrap startup errors with descriptive messages. - Created new tests for prompt functionalities, including workspace selection and script choices. - Implemented UI tests to verify color handling and header printing. - Added error handling tests for package.json reading in workspace functions.
Configure Prettier to match the existing style and replace the hand-maintained node --check list in the check script with a format check. Remove the commented-out header in ui.js and the empty config.example.json.
Run the Release workflow when CI completes successfully for a push to main, checking out the exact commit CI tested. Keep the manual trigger, queue concurrent releases, run the full check before publishing, and limit npm to ^11.5.1 for trusted publishing. Document the release flow in the README.
Detect each project's package manager from the packageManager field in package.json, then its lockfile, falling back to npm, and run scripts with pnpm, Yarn, Bun or npm accordingly. The project screen shows the detected tool and why it was chosen, and a missing tool produces an error with install instructions. CI installs pnpm, Yarn and Bun so every matrix job runs a real script with all four tools.
…cli#10) Co-authored-by: Grégoire FAVREAU <16638358+GregoireF@users.noreply.github.com>
… and script arguments (modulane/dev-workspace-cli#23)
…ace-cli The shared workflows came from modulane/dev-workspace-cli. Moving them here kept the code but not the commits, so the people who wrote them disappeared from this history. This merge adds the commits that touched those files, with their original authors and dates. It changes no file. Imported subjects start with [dev-workspace-cli] and their #N links point back to modulane/dev-workspace-cli, so they stay out of the release notes and do not trigger a release.
github-actions
Bot
added
maintenance
Contributor
Author
|
Hi @GregoireF |
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.
What and why
The shared workflows came from modulane/dev-workspace-cli. When I moved them here I only copied the files, so the commits stayed behind and the people who wrote them were missing from this repository's history: Grégoire Favreau hardened the workflows in modulane/dev-workspace-cli#10.
This brings that history back. The commits from dev-workspace-cli that touched the moved files (
.github/workflowsand.github/dependabot.yml, 20 commits) are merged in with their original authors and dates, through a single merge commit that changes no file: the tree is identical tomain.[dev-workspace-cli], so semantic-release does not parse them and they trigger no release (checked with the commit analyzer: no release type,minorfor a controlfeat:commit)#Nreferences in them point tomodulane/dev-workspace-cli#Ninstead of this repository's pull requestsMerge with "Create a merge commit", not squash: a squash would flatten the imported commits back into one commit and undo the fix.
AI use
Claude Code traced where the files came from, extracted and re-signed their history with
git filter-branch, made the merge, checked with semantic-release's commit analyzer that it triggers no release, and wrote this description. I reviewed the result.Checklist
feat:,fix:,docs:, …) and is lowercase🤖 Generated with Claude Code