repro-cli 0.2.0__tar.gz → 0.2.1__tar.gz

repro_cli-0.2.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Sukhdev Thukral
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

{repro_cli-0.2.0/repro_cli.egg-info → repro_cli-0.2.1}/PKG-INFO

@@ -1,16 +1,22 @@
 Metadata-Version: 2.4
 Name: repro-cli
-Version: 0.2.0
+Version: 0.2.1
 Summary: Disposable Docker environments for any GitHub issue
 Author: Sukhdev Thukral
 License-Expression: MIT
 Requires-Python: >=3.9
 Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
 
 # REPRO
+<img width="1279" height="238" alt="Screenshot 2026-08-09 203800" src="https://github.com/user-attachments/assets/f6c12a93-be02-45f3-a237-d310c24ac395" />
 
 > Disposable Docker environments for any GitHub issue.
 One command. No setup.
+<br>
+<img width="800" height="456" alt="ezgif com-video-to-gif-converter" src="https://github.com/user-attachments/assets/635990fc-ae46-4995-aded-c74b965c0c1d" />
+<br>
 
 ```bash
 pip install repro-cli
@@ -74,10 +80,10 @@ repro --help
 
 ## What it does
 
-1. **Parses** the GitHub issue URL
-2. **Detects** the repo's runtime - Node, Python, Go, Rust, Ruby, PHP, Java, or a devcontainer, based on whats actually in the repo.
+1. **Processes** the GitHub issue URL
+2. **Detects** the repo's runtime i.e Node, Python, Go, Rust, Ruby, PHP, Java, or a devcontainer based on whats actually in the repo.
 3. **Spins up** a disposable, isolated Docker container with the right base image.
-4. **Bind-mounts** a real folder on your machine into the container, so nothing is trapped - files persist after you exit
+4. **Bind-mounts** a real folder on your machine into the container, so nothing is trapped and files persist after you exit
 5. **Clones** the repo directly into that shared folder and install dependencies
 6. **Attaches VS Code directly to the running container** (auto-installing the Dev Containers extension if needed) - one window, one terminal, running *inside* the sandbox.
 7. *Destroys* the container the moment you exit. Your edited files remain exactly where they were.
@@ -86,9 +92,9 @@ repro --help
 
 ## The unified editor experience
 
-- **Real editor** — VS Code attaches directly into the container, so its built-in terminal *is* the sandbox shell. No second window to juggle.
-- **Real persistence** — because the folder is bind-mounted, not just cloned inside the container, your work survives after `exit`. Nothing is lost.
-If VS Code isn't installed, `repro` falls back gracefully — you still get a real folder path printed at the end, ready to open in whatever editor you use.
+- **Real editor**: VS Code attaches directly into the container, so its built-in terminal *is* the sandbox shell
+- **Real persistence**: because the folder is bind-mounted, not just cloned inside the container, your work survives after `exit`.
+If VS Code isn't installed, `repro` falls back gracefully, you still get a real folder path printed at the end, ready to open in whatever editor you use.
 
 ---
 
@@ -114,7 +120,7 @@ If VS Code isn't installed, `repro` falls back gracefully — you still get a re
 
 ## The GitHub App
 
-Install [**repro-sandbox-bot**](https://github.com/apps/repro-sandbox-bot) on any repo and it automatically comments the exact `repro` command on every new issue - so contributors never have to think about setup.
+Install [**repro-sandbox-bot**](https://github.com/apps/repro-sandbox-bot) on any repo and it automatically comments the exact `repro` command on every new issue, so that contributors never have to think about setup.
 
 ```
 🏖 Open this issue in DevSandbox

repro_cli-0.2.0/PKG-INFO → repro_cli-0.2.1/README.md

@@ -1,16 +1,11 @@
-Metadata-Version: 2.4
-Name: repro-cli
-Version: 0.2.0
-Summary: Disposable Docker environments for any GitHub issue
-Author: Sukhdev Thukral
-License-Expression: MIT
-Requires-Python: >=3.9
-Description-Content-Type: text/markdown
-
 # REPRO
+<img width="1279" height="238" alt="Screenshot 2026-08-09 203800" src="https://github.com/user-attachments/assets/f6c12a93-be02-45f3-a237-d310c24ac395" />
 
 > Disposable Docker environments for any GitHub issue.
 One command. No setup.
+<br>
+<img width="800" height="456" alt="ezgif com-video-to-gif-converter" src="https://github.com/user-attachments/assets/635990fc-ae46-4995-aded-c74b965c0c1d" />
+<br>
 
 ```bash
 pip install repro-cli
@@ -74,10 +69,10 @@ repro --help
 
 ## What it does
 
-1. **Parses** the GitHub issue URL
-2. **Detects** the repo's runtime - Node, Python, Go, Rust, Ruby, PHP, Java, or a devcontainer, based on whats actually in the repo.
+1. **Processes** the GitHub issue URL
+2. **Detects** the repo's runtime i.e Node, Python, Go, Rust, Ruby, PHP, Java, or a devcontainer based on whats actually in the repo.
 3. **Spins up** a disposable, isolated Docker container with the right base image.
-4. **Bind-mounts** a real folder on your machine into the container, so nothing is trapped - files persist after you exit
+4. **Bind-mounts** a real folder on your machine into the container, so nothing is trapped and files persist after you exit
 5. **Clones** the repo directly into that shared folder and install dependencies
 6. **Attaches VS Code directly to the running container** (auto-installing the Dev Containers extension if needed) - one window, one terminal, running *inside* the sandbox.
 7. *Destroys* the container the moment you exit. Your edited files remain exactly where they were.
@@ -86,9 +81,9 @@ repro --help
 
 ## The unified editor experience
 
-- **Real editor** — VS Code attaches directly into the container, so its built-in terminal *is* the sandbox shell. No second window to juggle.
-- **Real persistence** — because the folder is bind-mounted, not just cloned inside the container, your work survives after `exit`. Nothing is lost.
-If VS Code isn't installed, `repro` falls back gracefully — you still get a real folder path printed at the end, ready to open in whatever editor you use.
+- **Real editor**: VS Code attaches directly into the container, so its built-in terminal *is* the sandbox shell
+- **Real persistence**: because the folder is bind-mounted, not just cloned inside the container, your work survives after `exit`.
+If VS Code isn't installed, `repro` falls back gracefully, you still get a real folder path printed at the end, ready to open in whatever editor you use.
 
 ---
 
@@ -114,7 +109,7 @@ If VS Code isn't installed, `repro` falls back gracefully — you still get a re
 
 ## The GitHub App
 
-Install [**repro-sandbox-bot**](https://github.com/apps/repro-sandbox-bot) on any repo and it automatically comments the exact `repro` command on every new issue - so contributors never have to think about setup.
+Install [**repro-sandbox-bot**](https://github.com/apps/repro-sandbox-bot) on any repo and it automatically comments the exact `repro` command on every new issue, so that contributors never have to think about setup.
 
 ```
 🏖 Open this issue in DevSandbox

{repro_cli-0.2.0 → repro_cli-0.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name="repro-cli"
-version="0.2.0"
+version="0.2.1"
 description = "Disposable Docker environments for any GitHub issue"
 readme="README.md"
 requires-python=">=3.9"

repro_cli-0.2.0/README.md → repro_cli-0.2.1/repro_cli.egg-info/PKG-INFO

@@ -1,7 +1,22 @@
+Metadata-Version: 2.4
+Name: repro-cli
+Version: 0.2.1
+Summary: Disposable Docker environments for any GitHub issue
+Author: Sukhdev Thukral
+License-Expression: MIT
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
 # REPRO
+<img width="1279" height="238" alt="Screenshot 2026-08-09 203800" src="https://github.com/user-attachments/assets/f6c12a93-be02-45f3-a237-d310c24ac395" />
 
 > Disposable Docker environments for any GitHub issue.
 One command. No setup.
+<br>
+<img width="800" height="456" alt="ezgif com-video-to-gif-converter" src="https://github.com/user-attachments/assets/635990fc-ae46-4995-aded-c74b965c0c1d" />
+<br>
 
 ```bash
 pip install repro-cli
@@ -65,10 +80,10 @@ repro --help
 
 ## What it does
 
-1. **Parses** the GitHub issue URL
-2. **Detects** the repo's runtime - Node, Python, Go, Rust, Ruby, PHP, Java, or a devcontainer, based on whats actually in the repo.
+1. **Processes** the GitHub issue URL
+2. **Detects** the repo's runtime i.e Node, Python, Go, Rust, Ruby, PHP, Java, or a devcontainer based on whats actually in the repo.
 3. **Spins up** a disposable, isolated Docker container with the right base image.
-4. **Bind-mounts** a real folder on your machine into the container, so nothing is trapped - files persist after you exit
+4. **Bind-mounts** a real folder on your machine into the container, so nothing is trapped and files persist after you exit
 5. **Clones** the repo directly into that shared folder and install dependencies
 6. **Attaches VS Code directly to the running container** (auto-installing the Dev Containers extension if needed) - one window, one terminal, running *inside* the sandbox.
 7. *Destroys* the container the moment you exit. Your edited files remain exactly where they were.
@@ -77,9 +92,9 @@ repro --help
 
 ## The unified editor experience
 
-- **Real editor** — VS Code attaches directly into the container, so its built-in terminal *is* the sandbox shell. No second window to juggle.
-- **Real persistence** — because the folder is bind-mounted, not just cloned inside the container, your work survives after `exit`. Nothing is lost.
-If VS Code isn't installed, `repro` falls back gracefully — you still get a real folder path printed at the end, ready to open in whatever editor you use.
+- **Real editor**: VS Code attaches directly into the container, so its built-in terminal *is* the sandbox shell
+- **Real persistence**: because the folder is bind-mounted, not just cloned inside the container, your work survives after `exit`.
+If VS Code isn't installed, `repro` falls back gracefully, you still get a real folder path printed at the end, ready to open in whatever editor you use.
 
 ---
 
@@ -105,7 +120,7 @@ If VS Code isn't installed, `repro` falls back gracefully — you still get a re
 
 ## The GitHub App
 
-Install [**repro-sandbox-bot**](https://github.com/apps/repro-sandbox-bot) on any repo and it automatically comments the exact `repro` command on every new issue - so contributors never have to think about setup.
+Install [**repro-sandbox-bot**](https://github.com/apps/repro-sandbox-bot) on any repo and it automatically comments the exact `repro` command on every new issue, so that contributors never have to think about setup.
 
 ```
 🏖 Open this issue in DevSandbox
@@ -127,4 +142,4 @@ PRs welcome. Open an issue first for anything beyond small fixes - and yes, you
 
 ## License
 
-MIT
+MIT

{repro_cli-0.2.0 → repro_cli-0.2.1}/repro_cli.egg-info/SOURCES.txt

@@ -1,3 +1,4 @@
+LICENSE
 README.md
 pyproject.toml
 repro/__init__.py