|
1 | | -# Contributing to VS Code |
| 1 | +# Contributing to Roopik IDE |
2 | 2 |
|
3 | | -Welcome, and thank you for your interest in contributing to VS Code! |
| 3 | +Welcome, and thank you for your interest in contributing to Roopik! |
4 | 4 |
|
5 | | -There are several ways in which you can contribute, beyond writing code. The goal of this document is to provide a high-level overview of how you can get involved. |
| 5 | +## Ways to Contribute |
6 | 6 |
|
7 | | -## Asking Questions |
8 | | - |
9 | | - |
10 | | -Have a question? Instead of opening an issue, please ask on [Stack Overflow](https://stackoverflow.com/questions/tagged/visual-studio-code) using the tag `visual-studio-code`. |
11 | | - |
12 | | -The active community will be eager to assist you. Your well-worded question will serve as a resource to others searching for help. |
13 | | - |
14 | | -## Providing Feedback |
15 | | - |
16 | | -Your comments and feedback are welcome, and the development team is available via a handful of different channels. |
17 | | - |
18 | | -See the [Feedback Channels](https://github.com/microsoft/vscode/wiki/Feedback-Channels) wiki page for details on how to share your thoughts. |
| 7 | +- Report bugs and request features via [GitHub Issues](https://github.com/RoopikLabs/roopik/issues) |
| 8 | +- Submit pull requests for bug fixes or features |
| 9 | +- Improve documentation |
| 10 | +- Share feedback and ideas in [Discussions](https://github.com/RoopikLabs/roopik/discussions) |
19 | 11 |
|
20 | 12 | ## Reporting Issues |
21 | 13 |
|
22 | | -Have you identified a reproducible problem in VS Code? Do you have a feature request? We want to hear about it! Here's how you can report your issue as effectively as possible. |
23 | | - |
24 | | -### Identify Where to Report |
25 | | - |
26 | | -The VS Code project is distributed across multiple repositories. Try to file the issue against the correct repository. Check the list of [Related Projects](https://github.com/microsoft/vscode/wiki/Related-Projects) if you aren't sure which repo is correct. |
27 | | - |
28 | | -Can you recreate the issue even after [disabling all extensions](https://code.visualstudio.com/docs/editor/extension-gallery#_disable-an-extension)? If you find the issue is caused by an extension you have installed, please file an issue on the extension's repo directly. |
29 | | - |
30 | | -### Look For an Existing Issue |
31 | | - |
32 | | -Before you create a new issue, please do a search in [open issues](https://github.com/microsoft/vscode/issues) to see if the issue or feature request has already been filed. |
33 | | - |
34 | | -Be sure to scan through the [most popular](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc) feature requests. |
35 | | - |
36 | | -If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment: |
37 | | - |
38 | | -* 👍 - upvote |
39 | | -* 👎 - downvote |
40 | | - |
41 | | -If you cannot find an existing issue that describes your bug or feature, create a new issue using the guidelines below. |
42 | | - |
43 | | -### Writing Good Bug Reports and Feature Requests |
44 | | - |
45 | | -File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue. |
46 | | - |
47 | | -Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar but have different causes. |
48 | | - |
49 | | -The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix. |
50 | | - |
51 | | -The built-in tool for reporting an issue, which you can access by using `Report Issue` in VS Code's Help menu, can help streamline this process by automatically providing the version of VS Code, all your installed extensions, and your system info. Additionally, the tool will search among existing issues to see if a similar issue already exists. |
| 14 | +Before creating a new issue, please search [existing issues](https://github.com/RoopikLabs/roopik/issues) to avoid duplicates. |
52 | 15 |
|
53 | | -Please include the following with each issue: |
| 16 | +When reporting a bug, include: |
| 17 | +- Roopik version (Help > About) |
| 18 | +- Operating system |
| 19 | +- Steps to reproduce |
| 20 | +- Expected vs actual behavior |
| 21 | +- Screenshots or screen recordings if applicable |
| 22 | +- Errors from Developer Tools (Help > Toggle Developer Tools) |
54 | 23 |
|
55 | | -* Version of VS Code |
56 | | -* Your operating system |
57 | | -* List of extensions that you have installed |
58 | | -* Reproducible steps (1... 2... 3...) that cause the issue |
59 | | -* What you expected to see, versus what you actually saw |
60 | | -* Images, animations, or a link to a video showing the issue occurring |
61 | | -* A code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally |
62 | | - * **Note:** Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient. |
63 | | -* Errors from the Dev Tools Console (open from the menu: Help > Toggle Developer Tools) |
| 24 | +## Development Setup |
64 | 25 |
|
65 | | -### Creating Pull Requests |
| 26 | +### Prerequisites |
| 27 | +- Node.js (see `.nvmrc`) |
| 28 | +- Python 3.11+ |
| 29 | +- Git |
66 | 30 |
|
67 | | -* Please refer to the article on [creating pull requests](https://github.com/microsoft/vscode/wiki/How-to-Contribute#pull-requests) and contributing to this project. |
| 31 | +### Building from Source |
68 | 32 |
|
69 | | -### Final Checklist |
| 33 | +```bash |
| 34 | +# Clone |
| 35 | +git clone https://github.com/RoopikLabs/roopik.git |
| 36 | +cd roopik |
70 | 37 |
|
71 | | -Please remember to do the following: |
| 38 | +# Install dependencies |
| 39 | +npm install |
72 | 40 |
|
73 | | -* [ ] Search the issue repository to ensure your report is a new issue |
74 | | -* [ ] Recreate the issue after disabling all extensions |
75 | | -* [ ] Simplify your code around the issue to better isolate the problem |
| 41 | +# Watch (development) |
| 42 | +npm run watch |
76 | 43 |
|
77 | | -Don't feel bad if the developers can't reproduce the issue right away. They will simply ask for more information! |
| 44 | +# Build (production) |
| 45 | +npm run gulp vscode-win32-x64 # Windows |
| 46 | +npm run gulp vscode-darwin-arm64 # macOS |
| 47 | +npm run gulp vscode-linux-x64 # Linux |
| 48 | +``` |
78 | 49 |
|
79 | | -### Follow Your Issue |
| 50 | +### Building the Agent Dio Extension |
80 | 51 |
|
81 | | -Once submitted, your report will go into the [issue tracking](https://github.com/microsoft/vscode/wiki/Issue-Tracking) workflow. Be sure to understand what will happen next, so you know what to expect and how to continue to assist throughout the process. |
| 52 | +```bash |
| 53 | +cd extensions/roopik-roo |
| 54 | +npm install |
| 55 | +cd packages/types && npm install && npm run build && cd ../.. |
| 56 | +cd packages/build && npm install && npm run build && cd ../.. |
| 57 | +npm run build |
| 58 | +``` |
82 | 59 |
|
83 | | -## Automated Issue Management |
| 60 | +## Pull Requests |
84 | 61 |
|
85 | | -We use GitHub Actions to help us manage issues. These Actions and their descriptions can be [viewed here](https://github.com/microsoft/vscode-github-triage-actions). Some examples of what these Actions do are: |
| 62 | +1. Fork the repository |
| 63 | +2. Create a feature branch (`git checkout -b feat/my-feature`) |
| 64 | +3. Make your changes |
| 65 | +4. Test locally (build + run) |
| 66 | +5. Commit with a clear message |
| 67 | +6. Push and open a Pull Request |
86 | 68 |
|
87 | | -* Automatically close any issue marked `info-needed` if there has been no response in the past 7 days. |
88 | | -* Automatically lock issues 45 days after they are closed. |
89 | | -* Automatically implement the VS Code [feature request pipeline](https://github.com/microsoft/vscode/wiki/Issues-Triaging#managing-feature-requests). |
| 69 | +### PR Guidelines |
90 | 70 |
|
91 | | -If you believe the bot got something wrong, please open a new issue and let us know. |
| 71 | +- Keep PRs focused - one feature or fix per PR |
| 72 | +- Include a clear description of what changed and why |
| 73 | +- Add screenshots for UI changes |
| 74 | +- Ensure the build passes before submitting |
92 | 75 |
|
93 | | -## Contributing Fixes |
| 76 | +## Project Structure |
94 | 77 |
|
95 | | -If you are interested in writing code to fix issues, please see [How to Contribute](https://github.com/microsoft/vscode/wiki/How-to-Contribute) in the wiki. |
| 78 | +- `src/vs/workbench/contrib/roopik/` — Core Roopik features (Canvas, Project,Browser, MCP, tools) |
| 79 | +- `extensions/roopik-roo/` — Dio agent (built on Roo Code) |
96 | 80 |
|
97 | | -## Thank You |
| 81 | +## License |
98 | 82 |
|
99 | | -Your contributions to open source, large or small, make great projects like this possible. Thank you for taking the time to contribute. |
| 83 | +By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE.txt). |
0 commit comments