chore: update links after repository transfer

trunk-rs · Dec 12, 2023 · 2d6cc62 · 2d6cc62
1 parent cdddc60
commit 2d6cc62
Show file tree

Hide file tree

Showing 9 changed files with 17 additions and 19 deletions.
diff --git a/Cargo.toml b/Cargo.toml
@@ -8,7 +8,7 @@ authors = [
     "Anthony Dodd <[email protected]>",
     "Jens Reimann <[email protected]>"
 ]
-repository = "https://github.com/thedodd/trunk"
+repository = "https://github.com/trunk-rs/trunk"
 readme = "README.md"
 categories = ["command-line-utilities", "wasm", "web-programming"]
 keywords = ["wasm", "bundler", "web", "build-tool", "compiler"]

diff --git a/README.md b/README.md
@@ -1,11 +1,11 @@
 # Trunk
 
-[![Build Status](https://github.com/thedodd/trunk/actions/workflows/ci.yaml/badge.svg?branch=trunk)](https://github.com/thedodd/trunk/actions)
+[![Build Status](https://github.com/trunk-rs/trunk/actions/workflows/ci.yaml/badge.svg?branch=trunk)](https://github.com/trunk-rs/trunk/actions)
 [![](https://img.shields.io/crates/v/trunk.svg?color=brightgreen&style=flat-square)](https://crates.io/crates/trunk)
 ![](https://img.shields.io/badge/license-MIT%2FApache--2.0-blue?style=flat-square)
 [![Discord Chat](https://img.shields.io/discord/793890238267260958?logo=discord&style=flat-square)](https://discord.gg/JEPdBujTDr)
 [![](https://img.shields.io/crates/d/trunk?label=downloads%20%28crates.io%29&style=flat-square)](https://crates.io/crates/trunk)
-[![](https://img.shields.io/github/downloads/thedodd/trunk/total?label=downloads%20%28GH%29&style=flat-square)](https://github.com/thedodd/trunk/releases)
+[![](https://img.shields.io/github/downloads/trunk-rs/trunk/total?label=downloads%20%28GH%29&style=flat-square)](https://github.com/trunk-rs/trunk/releases)
 ![](https://img.shields.io/homebrew/installs/dy/trunk?color=brightgreen&label=downloads%20%28brew%29&style=flat-square)
 
 **Build, bundle & ship your Rust WASM application to the web.**
@@ -23,9 +23,9 @@ Trunk is a WASM web application bundler for Rust. Trunk uses a simple, optional-
 Head on over to the [Trunk website](https://trunkrs.dev), everything you need is there. A few quick links:
 
 - [Install](https://trunkrs.dev/#install)
-  - Download a released binary: https://github.com/thedodd/trunk/releases
+  - Download a released binary: https://github.com/trunk-rs/trunk/releases
   - `cargo binstall trunk`
-  - `cargo install --git https://github.com/thedodd/trunk trunk` (most recent from git)
+  - `cargo install --git https://github.com/trunk-rs/trunk trunk` (most recent from git)
   - `cargo install --path . trunk` (Most recent from local directory)
 - [App Setup](https://trunkrs.dev//#app-setup)
 - [Assets](https://trunkrs.dev/assets/)

diff --git a/examples/yew-tailwindcss/src/main.rs b/examples/yew-tailwindcss/src/main.rs
@@ -22,9 +22,10 @@ impl Component for App {
     }
 
     fn view(&self) -> Html {
-        let link_classes = "block px-4 py-2 hover:bg-black hover:text-white rounded border-black border";
+        let link_classes =
+            "block px-4 py-2 hover:bg-black hover:text-white rounded border-black border";
         let links = [
-            ("Trunk", "https://github.com/thedodd/trunk"),
+            ("Trunk", "https://github.com/trunk-rs/trunk"),
             ("Yew", "https://yew.rs/"),
             ("Tailwind", "https://tailwindcss.com"),
         ];

diff --git a/examples/yew/src/main.rs b/examples/yew/src/main.rs
@@ -39,7 +39,7 @@ impl Component for App {
                 navend=html!{
                     <>
                     <ybc::NavbarItem>
-                        <ybc::ButtonAnchor classes=classes!("is-black", "is-outlined") rel=String::from("noopener noreferrer") target=String::from("_blank") href="https://github.com/thedodd/trunk">
+                        <ybc::ButtonAnchor classes=classes!("is-black", "is-outlined") rel=String::from("noopener noreferrer") target=String::from("_blank") href="https://github.com/trunk-rs/trunk">
                             {"Trunk"}
                         </ybc::ButtonAnchor>
                     </ybc::NavbarItem>

diff --git a/site/config.toml b/site/config.toml
@@ -15,5 +15,5 @@ favicon = "rustacean-flat-happy.svg"
 juice_logo_name = "Trunk"
 juice_logo_path = "rustacean-flat-happy.svg"
 juice_extra_menu = [
-    { title = "Github", link = "https://github.com/thedodd/trunk"}
+    { title = "Github", link = "https://github.com/trunk-rs/trunk"}
 ]
diff --git a/site/content/_index.md b/site/content/_index.md
@@ -29,12 +29,12 @@ cargo binstall trunk
 
 ### GitHub release download
 
-Fetch and unpack a released binary from the [release page](https://github.com/thedodd/trunk/releases).
+Fetch and unpack a released binary from the [release page](https://github.com/trunk-rs/trunk/releases).
 
 For example (be sure to check for the most recent version):
 
 ```shell
-wget -qO- https://github.com/thedodd/trunk/releases/download/0.17.10/trunk-x86_64-unknown-linux-gnu.tar.gz | tar -xzf-
+wget -qO- https://github.com/trunk-rs/trunk/releases/download/0.17.10/trunk-x86_64-unknown-linux-gnu.tar.gz | tar -xzf-
 ```
 
 ### NixOS
@@ -47,9 +47,6 @@ nix-env -i trunk
 
 ### Brew
 
-**Note:** Brew isn't supported at the moment. There is a PR pending, however it seems to publishing a fork of something
-without acknowledging it's a fork isn't something that Homebrew does: https://github.com/Homebrew/homebrew-core/pull/150913
-
 ```shell
 brew install trunk
 ```
@@ -124,7 +121,7 @@ That's not all! Trunk has even more useful features. Head on over to the followi
 
 # Contributing
 
-Anyone and everyone is welcome to contribute! Please review the [CONTRIBUTING.md](https://github.com/thedodd/trunk/blob/master/CONTRIBUTING.md) document for more details. The best way to get started is to find an open issue, and then start hacking on implementing it. Letting other folks know that you are working on it, and sharing progress is a great approach. Open pull requests early and often, and please use GitHub's draft pull request feature.
+Anyone and everyone is welcome to contribute! Please review the [CONTRIBUTING.md](https://github.com/trunk-rs/trunk/blob/master/CONTRIBUTING.md) document for more details. The best way to get started is to find an open issue, and then start hacking on implementing it. Letting other folks know that you are working on it, and sharing progress is a great approach. Open pull requests early and often, and please use GitHub's draft pull request feature.
 
 # License
 

diff --git a/site/content/assets.md b/site/content/assets.md
@@ -50,7 +50,7 @@ This will typically look like: `<link data-trunk rel="{type}" href="{path}" ..ot
 
 ✅ `rel="css"`: Trunk will copy linked css files found in the source HTML without content modification. This content is hashed for cache control. The `href` attribute must be included in the link pointing to the css file to be processed.
 
-  - In the future, Trunk will resolve local `@imports`, will handle minification (see [trunk#7](https://github.com/thedodd/trunk/issues/7)), and we may even look into a pattern where any CSS found in the source tree will be bundled, which would enable a nice zero-config "component styles" pattern. See [trunk#3](https://github.com/thedodd/trunk/issues/3) for more details.
+  - In the future, Trunk will resolve local `@imports`, will handle minification (see [trunk#7](https://github.com/trunk-rs/trunk/issues/7)), and we may even look into a pattern where any CSS found in the source tree will be bundled, which would enable a nice zero-config "component styles" pattern. See [trunk#3](https://github.com/trunk-rs/trunk/issues/3) for more details.
   - `data-integrity`: (optional) the `integrity` digest type for code & script resources. Defaults to plain `sha384`.
 
 ## tailwind
@@ -111,7 +111,7 @@ Images and other resource types can be copied into the `dist` dir by adding a li
 
 This will allow your WASM application to reference images directly from the `dist` dir, and Trunk will ensure that the images are available in the `dist` dir to be served.
 
-**NOTE:** as Trunk continues to mature, we will find better ways to include images and other resources. Hashing content for cache control is great, we just need to find a nice pattern to work with images referenced in Rust components. Please contribute to the discussion over in [trunk#9](https://github.com/thedodd/trunk/issues/9)! See you there.
+**NOTE:** as Trunk continues to mature, we will find better ways to include images and other resources. Hashing content for cache control is great, we just need to find a nice pattern to work with images referenced in Rust components. Please contribute to the discussion over in [trunk#9](https://github.com/trunk-rs/trunk/issues/9)! See you there.
 
 # Sub-resource integrity (SRI)
 

diff --git a/site/content/configuration.md b/site/content/configuration.md
@@ -7,7 +7,7 @@ weight = 2
 Trunk supports a layered config system. At the base, a config file can encapsulate project specific defaults, paths, ports and other config. Environment variables can be used to overwrite config file values. Lastly, CLI arguments / options take final precedence.
 
 # Trunk.toml
-Trunk supports an optional `Trunk.toml` config file. An example config file is included [in the Trunk repo](https://github.com/thedodd/trunk/blob/master/Trunk.toml), and shows all available config options along with their default values. By default, Trunk will look for a `Trunk.toml` config file in the current working directory. Trunk supports the global `--config` option to specify an alternative location for the file.
+Trunk supports an optional `Trunk.toml` config file. An example config file is included [in the Trunk repo](https://github.com/trunk-rs/trunk/blob/master/Trunk.toml), and shows all available config options along with their default values. By default, Trunk will look for a `Trunk.toml` config file in the current working directory. Trunk supports the global `--config` option to specify an alternative location for the file.
 
 Note that any relative paths declared in a `Trunk.toml` file will be treated as being relative to the `Trunk.toml` file itself.
 

diff --git a/site/templates/index.html b/site/templates/index.html
@@ -56,7 +56,7 @@ <h3 class="title-text">
 <footer>
     <p>
         <small class="subtext text-center">
-            <a href="https://github.com/thedodd/trunk">Trunk Maintainers</a> © 2023
+            <a href="https://github.com/trunk-rs/trunk">Trunk Maintainers</a> © 2023
         </small>
     </p>
     <p class="subtext text-center">