Feature/npm package updates #9
Merged
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.
This pull request introduces the initial public release of the Git Context Switcher project, version 1.0.0, along with comprehensive documentation and implementation details. The most significant changes include the addition of a changelog, updates to the README for installation and usage instructions, enhancements to the main script (
index.js), and a roadmap for future development innext-steps.md.Key Changes
Initial Release and Documentation:
CHANGELOG.mdto track all notable changes, adhering to Semantic Versioning and Keep a Changelog standards. The changelog documents the initial public release and its features, including an interactive setup wizard, multiple context support, and CLI commands.README.mdwith detailed installation instructions (via npm), feature descriptions, and usage examples for commands likesetupandapply. Removed redundant global installation instructions. [1] [2] [3] [4] [5]Code Enhancements:
index.jsto dynamically read the version frompackage.jsonusingfsandpathmodules. Improved consistency by switching to double quotes for strings throughout the file.Future Development:
next-steps.mdoutlining the project's current status, high-priority tasks (e.g., error handling improvements, documentation enhancements, and increased test coverage), and a roadmap for future features and releases following Semantic Versioning.