From 8b4c43f72de1652c60ee921956f1cff244b06136 Mon Sep 17 00:00:00 2001 From: Nyk <0xnykcd@googlemail.com> Date: Wed, 4 Mar 2026 00:18:30 +0700 Subject: [PATCH] fix: align repo links and updater endpoint after transfer --- BUILD.md | 2 +- CONTRIBUTING.md | 28 ++++++++++++++-------------- README.md | 2 +- src-tauri/src/llm_client.rs | 4 ++-- src-tauri/tauri.conf.json | 2 +- 5 files changed, 19 insertions(+), 19 deletions(-) diff --git a/BUILD.md b/BUILD.md index 252d8b9..91d0e56 100644 --- a/BUILD.md +++ b/BUILD.md @@ -52,7 +52,7 @@ This guide covers how to set up the development environment and build Dictx from ### 1. Clone the Repository ```bash -git clone git@github.com:0xNyk/dictx.git +git clone git@github.com:splitlabs/dictx.git cd dictx ``` diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f447044..514f416 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -37,7 +37,7 @@ Before you begin, ensure you have the following installed: 3. **Add upstream remote**: ```bash - git remote add upstream git@github.com:0xNyk/dictx.git + git remote add upstream git@github.com:splitlabs/dictx.git ``` 4. **Install dependencies**: @@ -88,8 +88,8 @@ For more details, see the Architecture section in [README.md](README.md) or [AGE ### Before Submitting a Bug Report -1. **Search existing issues** at [github.com/cjpais/Handy/issues](https://github.com/0xNyk/dictx/issues) -2. **Check discussions** at [github.com/cjpais/Handy/discussions](https://github.com/0xNyk/dictx/discussions) +1. **Search existing issues** at [github.com/cjpais/Handy/issues](https://github.com/splitlabs/dictx/issues) +2. **Check discussions** at [github.com/cjpais/Handy/discussions](https://github.com/splitlabs/dictx/discussions) 3. **Try the latest release** to see if the issue has been fixed 4. **Enable debug mode** (`Cmd/Ctrl+Shift+D`) to gather diagnostic information @@ -121,14 +121,14 @@ We use GitHub Discussions for feature requests rather than issues. This keeps is ### Before Suggesting a Feature -1. **Search existing discussions** at [github.com/cjpais/Handy/discussions](https://github.com/0xNyk/dictx/discussions) +1. **Search existing discussions** at [github.com/cjpais/Handy/discussions](https://github.com/splitlabs/dictx/discussions) 2. **Check common feature requests**: - - [Post-processing / Editing Transcripts](https://github.com/0xNyk/dictx/discussions/168) - - [Keyboard Shortcuts / Hotkeys](https://github.com/0xNyk/dictx/discussions/211) + - [Post-processing / Editing Transcripts](https://github.com/splitlabs/dictx/discussions/168) + - [Keyboard Shortcuts / Hotkeys](https://github.com/splitlabs/dictx/discussions/211) ### Submitting a Feature Request -1. Go to [Discussions](https://github.com/0xNyk/dictx/discussions) +1. Go to [Discussions](https://github.com/splitlabs/dictx/discussions) 2. Click "New discussion" 3. Choose the appropriate category (Ideas, Feature Requests, etc.) 4. Describe your feature idea including: @@ -144,14 +144,14 @@ We use GitHub Discussions for feature requests rather than issues. This keeps is **This is critical:** Before writing any code, please do the following: 1. **Search existing issues and PRs** - Check both open AND closed issues and pull requests. Someone may have already addressed this, or there may be a reason it was closed. - - [Open issues](https://github.com/0xNyk/dictx/issues) - - [Closed issues](https://github.com/0xNyk/dictx/issues?q=is%3Aissue+is%3Aclosed) - - [Open PRs](https://github.com/0xNyk/dictx/pulls) - - [Closed PRs](https://github.com/0xNyk/dictx/pulls?q=is%3Apr+is%3Aclosed) + - [Open issues](https://github.com/splitlabs/dictx/issues) + - [Closed issues](https://github.com/splitlabs/dictx/issues?q=is%3Aissue+is%3Aclosed) + - [Open PRs](https://github.com/splitlabs/dictx/pulls) + - [Closed PRs](https://github.com/splitlabs/dictx/pulls?q=is%3Apr+is%3Aclosed) 2. **If something was previously closed** - If you want to revisit a closed issue or PR, you need to: - Provide a strong argument for why it should be reconsidered - - Gather community feedback first via [Discussions](https://github.com/0xNyk/dictx/discussions) + - Gather community feedback first via [Discussions](https://github.com/splitlabs/dictx/discussions) - Link to that discussion in your PR 3. **Get community feedback for features** - PRs with demonstrated community interest are **much more likely to be merged**. Start a discussion, get feedback, and link to it in your PR. This helps ensure Dictx stays focused and useful without becoming bloated. @@ -209,7 +209,7 @@ We use GitHub Discussions for feature requests rather than issues. This keeps is ``` 7. **Create a Pull Request**: - - Go to the [Dictx repository](https://github.com/0xNyk/dictx) + - Go to the [Dictx repository](https://github.com/splitlabs/dictx) - Click "New Pull Request" - Select your fork and branch - Fill out the PR template completely, including: @@ -303,7 +303,7 @@ Look for issues labeled `good first issue` or `help wanted` if you're new to the ## 📞 Getting Help -- **Discussions**: Ask questions in [GitHub Discussions](https://github.com/0xNyk/dictx/discussions) +- **Discussions**: Ask questions in [GitHub Discussions](https://github.com/splitlabs/dictx/discussions) ## 📜 License diff --git a/README.md b/README.md index c499839..49959c6 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ Built with [Tauri](https://tauri.app) (Rust + React/TypeScript). Forked from [Ha ## Installation -Download the latest release for your platform from the [Releases page](https://github.com/0xNyk/dictx/releases). +Download the latest release for your platform from the [Releases page](https://github.com/splitlabs/dictx/releases). | Platform | Format | | -------- | -------------------- | diff --git a/src-tauri/src/llm_client.rs b/src-tauri/src/llm_client.rs index 6a6d350..fc11482 100644 --- a/src-tauri/src/llm_client.rs +++ b/src-tauri/src/llm_client.rs @@ -55,11 +55,11 @@ fn build_headers(provider: &PostProcessProvider, api_key: &str) -> Result