Thank you for taking the time to improve MiniSnip. The project values predictable behavior, low resource usage, and changes that remain easy to audit.
- Search for an existing issue before creating a new one.
- Open an issue first when proposing a significant user interface or behavior change.
- Keep changes focused. Avoid unrelated refactors.
MiniSnip builds on Windows with .NET Framework 4.x:
git clone https://github.com/Mirochill/MiniSnip.git
cd MiniSnip
.\build.ps1
.\test.ps1- Preserve Windows 10 and Windows 11 compatibility.
- Do not add telemetry or implicit network communication.
- Keep screenshots local and clipboard-based.
- Avoid third-party dependencies when a Windows or .NET Framework API is sufficient.
- Add or update tests when behavior changes.
- Run
.\build.ps1and.\test.ps1before opening a pull request. - Measure the impact of changes to performance-sensitive paths, especially overlay painting and mouse event handling.
Describe the problem, the selected approach, and the checks you ran. Include before-and-after screenshots when intentionally modifying the interface.
By submitting a contribution, you agree that it will be distributed under the project's MIT License.