ci: ⚙️fix publish issue

Author: hks2002

.vscodeignore

@@ -12,3 +12,5 @@ vsc-extension-quickstart.md
 **/*.map
 esbuild.config.js
 eslint.config.mjs
+cspell.json
+cspell.project-words.txt

l10n/bundle.l10n.json l10n/bundle.jsonl10n/bundle.l10n.json renamed to l10n/bundle.json

@@ -2,17 +2,18 @@
  * @Author                : Robert Huang<56649783@qq.com>                     *
  * @CreatedDate           : 2023-02-04 10:01:21                               *
  * @LastEditors           : Robert Huang<56649783@qq.com>                     *
- * @LastEditDate          : 2026-01-18 14:45:00                               *
+ * @LastEditDate          : 2026-01-18 16:28:42                               *
  * @FilePath              : emoji-commit-tiny/src/extension.js                *
  * @CopyRight             : MerBleueAviation                                  *
  *****************************************************************************/
 
+
 // The module 'vscode' contains the VS Code extensibility API
 // Import the module and reference it with the alias vscode in your code below
 import i18next from 'i18next'
 import * as vscode from 'vscode'
-import l10nEn from '../l10n/bundle.l10n.json'
-import l10nZh from '../l10n/bundle.l10n.zh-cn.json'
+import l10nEn from '../l10n/bundle.json'
+import l10nZh from '../l10n/bundle.zh-cn.json'
 import packageJson from '../package.json'
 import { Logger } from './logger'
 import { emojiCommit } from './utils'

l10n/bundle.l10n.zh-cn.json l10n/bundle.zh-cn.jsonl10n/bundle.l10n.zh-cn.json renamed to l10n/bundle.zh-cn.json

@@ -0,0 +1,47 @@
+# 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.
+* `src/extension.ts` - 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 `src/extension.ts` 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 `src/extension.ts`.
+* 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.ts` 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.
+
+## Publish your extension
+
+* Follow the [working with extensions](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) guide to create a publisher account on the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/).
+* Update the `PAT` from [Azure DevOps](https://dev.azure.com/your-organization/_usersSettings/tokens);
+* Run `vsce publish` to publish your extension to the marketplace.
+
+## 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.
+ * Reduce the extension size and improve the startup time by [bundling your extension](https://code.visualstudio.com/api/working-with-extensions/bundling-extension).
+ * Automate builds by setting up [Continuous Integration](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).