qwe (pronounced kiwi) offers a streamlined and efficient approach to version/revision control, focusing on individual file tracking rather than entire projects. Unlike traditional systems like Git that manage repositories as a whole, qwe allows users to monitor file changes independently, making it ideal for quick-level tracking, experimentation, or handling standalone scripts.

Key Features

• File-based Version Control: Easily track versions of specific files without managing the entire project.
• Effortless Commits: Save changes with straightforward commit messages.
• Flexible Reversion: Seamlessly roll back a single file without impacting others.
• Speed and Simplicity: Designed for minimal setup and management, enabling quick file control.

Commands Overview

Utilizing qwe is simple and user-friendly. Key commands include:

Example Usage

qwe init
qwe track notes.txt
qwe commit notes.txt "Initial notes added" // -> commitID 0
qwe commit notes.txt "Updated with new ideas" // -> commitID 1
qwe commit notes.txt "Removed already executed ideas" // -> commitID 2
qwe list notes.txt
qwe revert notes.txt 1
qwe current notes.txt
qwe diff notes.txt
qwe rebase notes.txt

Advantages of Using qwe

• Tailored for independent file tracking without the overhead of a complete Git repository.
• Suitable for managing scripts, configurations, notes, or any document that requires individual version tracking.
• CLI interface is designed for ease of use, eliminating the complexities of branching and merging common in other version control systems.

Future Enhancements

The roadmap for qwe includes exciting features such as grouped snapshots, remote file synchronization and the potential for a GUI interface, aimed at enhancing user experience in file management.

Embrace the simplicity and efficiency of file-level version control with qwe, designed for those who prioritize streamlined tracking over complex setup.