Merge pull request #28 from Iheuzio/update/logo

Update/logo

CHANGELOG.md

@@ -4,6 +4,21 @@ Version History
 
 ## [Unreleased]
 
+## [Release 0.2.0]
+
+- Copy code
+- Auto response
+- Formatting
+
+## What's Changed
+* Feature/format code by @Iheuzio in https://github.com/Iheuzio/gpt-contextfiles/pull/23
+* update(gif): Added new gif to reflect program by @Iheuzio in https://github.com/Iheuzio/gpt-contextfiles/pull/24
+* feature(code-box): Can copy code and load responses by @Iheuzio in https://github.com/Iheuzio/gpt-contextfiles/pull/25
+* Release 0.2.0 by @Iheuzio in https://github.com/Iheuzio/gpt-contextfiles/pull/26
+
+
+**Full Changelog**: https://github.com/Iheuzio/gpt-contextfiles/compare/0.1.3...0.2.0
+
 ## [Release 0.1.3]
 
 ## What's Changed

README.md

@@ -28,11 +28,12 @@ Submit -> Submits the query to the api
 
 Refresh -> refreshes the window so that all new files will be available for that session.
 
+Click -> Click the orange code and then paste it in your editor for fast coding
+
 - Right click to add files to the context window
 - Click on the extension addon to open the context window, refresh to update the files to check.
 - Select the files uses checkboxes
 - Wait for response to be returned
-- Copy the code (orange portion) and paste it into your code editor
 
 # How it works
 

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "gpt-contextfiles",
-  "version": "0.0.1",
+  "version": "0.2.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "gpt-contextfiles",
-      "version": "0.0.1",
+      "version": "0.2.1",
       "dependencies": {
         "openai": "^3.3.0"
       },

package.json

@@ -1,8 +1,8 @@
 {
   "name": "gpt-contextfiles",
   "displayName": "GPT-ContextFiles",
-  "description": "Choose the files to pass into GPT to provide a question with multiple files (doesn't check context)",
+  "description": "Choose the files to pass into GPT to provide a question with multiple files",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "engines": {
     "vscode": "^1.79.0"
   },
@@ -22,7 +22,12 @@
     "testing",
     "debugging",
     "files",
-    "api"
+    "api",
+    "snippets",
+    "openai",
+    "vscode",
+    "extension",
+    "chatbot"
   ],
   "relatedTags": [
     "Artificial Intelligence",
@@ -115,6 +120,6 @@
     "type": "git",
     "url": "https://github.com/Iheuzio/gpt-contextfiles/"
   },
-  "icon": "images/gpt-icon.jpg",
+  "icon": "images/gpt-icon.png",
   "publisher": "Iheuzio"
 }

vsc-extension-quickstart.md

@@ -1,41 +0,0 @@
-# Welcome to your VS Code Extension
-
-## What's in the folder
-
-* This folder contains all of the files necessary for your extension.
-* `package.json` - this is the manifest file in which you declare your extension and command.
-  * The sample plugin registers a command and defines its title and command name. With this information VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
-* `extension.js` - this is the main file where you will provide the implementation of your command.
-  * The file exports one function, `activate`, which is called the very first time your extension is activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
-  * We pass the function containing the implementation of the command as the second parameter to `registerCommand`.
-
-## Get up and running straight away
-
-* Press `F5` to open a new window with your extension loaded.
-* Run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`.
-* Set breakpoints in your code inside `extension.js` to debug your extension.
-* Find output from your extension in the debug console.
-
-## Make changes
-
-* You can relaunch the extension from the debug toolbar after changing code in `extension.js`.
-* You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes.
-
-## Explore the API
-
-* You can open the full set of our API when you open the file `node_modules/@types/vscode/index.d.ts`.
-
-## Run tests
-
-* Open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Extension Tests`.
-* Press `F5` to run the tests in a new window with your extension loaded.
-* See the output of the test result in the debug console.
-* Make changes to `src/test/suite/extension.test.js` or create new test files inside the `test/suite` folder.
-  * The provided test runner will only consider files matching the name pattern `**.test.ts`.
-  * You can create folders inside the `test` folder to structure your tests any way you want.
-
-## Go further
-
- * [Follow UX guidelines](https://code.visualstudio.com/api/ux-guidelines/overview) to create extensions that seamlessly integrate with VS Code's native interface and patterns.
- * [Publish your extension](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) on the VS Code extension marketplace.
- * Automate builds by setting up [Continuous Integration](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).