Fix repo/source references

Author: AugustMiller

docs/3.x/extend/extending-system-components.md

@@ -8,7 +8,7 @@ updatedVersion: 4.x/extend/topics.md
 
 You can add your own custom validation rules to elements and other system components using the [EVENT_DEFINE_RULES](craft3:craft\base\Model#event-define-rules) event.
 
-Additional rules can use any of [Yii’s core validators](https://www.yiiframework.com/doc/guide/2.0/en/tutorial-core-validators), [Craft’s validators](https://github.com/craftcms/cms/tree/develop/src/validators), or an [inline validation method](https://www.yiiframework.com/doc/guide/2.0/en/input-validation#inline-validators).
+Additional rules can use any of [Yii’s core validators](https://www.yiiframework.com/doc/guide/2.0/en/tutorial-core-validators), [Craft’s validators](repo:craftcms/cms/tree/3.x/src/validators), or an [inline validation method](https://www.yiiframework.com/doc/guide/2.0/en/input-validation#inline-validators).
 
 In this example, we’re adding a 5-item maximum for custom entry fields in a “News” section. It uses Craft’s `ArrayValidator` to easily validate based on the size of an array or element query result (like the Tags field):
 

docs/3.x/extend/graphql.md

@@ -23,18 +23,18 @@ Craft relies on the [webonyx/graphql-php](https://github.com/webonyx/graphql-php
 Be mindful of Craft vs. GraphQL terminology, because there are overlapping terms that can be confusing. It helps to pay careful attention to namespacing when looking at code examples.
 :::
 
-The rest of this page will cover each of the main things you may need to work with. If you’d like some concrete examples, have a look at Craft’s own pieces in the [`src/gql/` directory](https://github.com/craftcms/cms/tree/main/src/gql).
+The rest of this page will cover each of the main things you may need to work with. If you’d like some concrete examples, have a look at Craft’s own pieces in the [`src/gql/` directory](repo:craftcms/cms/tree/3.x/src/gql).
 
 ### Limitations
 
 If you’re planning advanced or elaborate GraphQL features, please be aware of the following limitations with Craft’s GraphQL implementation:
 
 - GraphQL subscriptions aren’t currently supported.
-- Advanced query builder functions [are not exposed for GraphQL](https://github.com/craftcms/cms/issues/7842).
+- Advanced query builder functions [are not exposed for GraphQL](repo:craftcms/cms/issues/7842).
 
 ## Folder Structure
 
-Here’s a high-level look at the folder structure we’ll explore in our example adding a “Widget” element. You can structure things however you want, we’re just following [Craft’s organization](https://github.com/craftcms/cms/tree/main/src/gql):
+Here’s a high-level look at the folder structure we’ll explore in our example adding a “Widget” element. You can structure things however you want, we’re just following [Craft’s organization](repo:craftcms/cms/tree/3.x/src/gql):
 
 ```treeview
 src/gql/

docs/3.x/extend/module-guide.md

@@ -8,7 +8,7 @@ Before you begin working on a module, you need to decide on a couple things:
 - **Module ID** – Something that uniquely identifies your plugin within your project. (Module IDs must begin with a letter and contain only lowercase letters, numbers, and dashes. They should be `kebab-cased`.)
 
 ::: warning
-When choosing a module ID, try to avoid names that will conflict with Craft’s core [controllers](https://github.com/craftcms/cms/tree/develop/src/controllers) (e.g. `app` would conflict with `AppController.php`), as well as any installed plugin handles. Otherwise bad things will happen.
+When choosing a module ID, try to avoid names that will conflict with Craft’s core [controllers](repo:craftcms/cms/tree/3.x/src/controllers) (e.g. `app` would conflict with `AppController.php`), as well as any installed plugin handles. Otherwise bad things will happen.
 :::
 
 ## Set up the basic file structure

docs/4.x/config/app.md

@@ -5,7 +5,7 @@ Craft’s entire [application configuration](https://www.yiiframework.com/doc/gu
 You can further customize the application configuration for only web requests or console requests from `config/app.web.php` and `config/app.console.php`.
 
 ::: warning
-New [Craft projects](https://github.com/craftcms/craft/tree/4.x) include a stub of `app.php` that exists solely to set an app ID, which affects how caches and sessions are stored. Most applications will _not_ require additional application config.
+New [Craft projects](repo:craftcms/craft/tree/4.x) include a stub of `app.php` that exists solely to set an app ID, which affects how caches and sessions are stored. Most applications will _not_ require additional application config.
 :::
 
 ## Approach
@@ -444,7 +444,7 @@ return [
 ];
 ```
 
-Available drivers are listed in the [Yii2 Queue Extension documentation](https://github.com/yiisoft/yii2-queue/tree/master/docs/guide).
+Available drivers are listed in the [Yii2 Queue Extension documentation](repo:yiisoft/yii2-queue/tree/master/docs/guide).
 
 ::: warning
 Only drivers that implement <craft4:craft\queue\QueueInterface> will be visible within the control panel.

docs/4.x/control-panel.md

@@ -121,7 +121,7 @@ Keep in mind that any user marked as an “Admin” implicitly has access to _al
 
 #### Disabling Utilities
 
-You can disable a utility for all users with the [`disabledUtilities` config setting](config4:disabledUtilities). <Since ver="4.6.0" feature="Disabling utilities" /> Refer to each [utility class](repo:craftcms/cms/tree/main/src/utilities)’s `id()` method for their handles—including those provided by plugins.
+You can disable a utility for all users with the [`disabledUtilities` config setting](config4:disabledUtilities). <Since ver="4.6.0" feature="Disabling utilities" /> Refer to each [utility class](repo:craftcms/cms/tree/4.x/src/utilities)’s `id()` method for their handles—including those provided by plugins.
 
 ### Settings
 

docs/4.x/dev/controller-actions.md

@@ -460,7 +460,7 @@ The value of `modelName` in a JSON response is the same as the variable name Cra
 
 ## Available Actions
 
-This is not a comprehensive list! We have selected a few actions to illustrate fundamentals that many projects can benefit from—and to get you prepared to explore the rest of Craft’s [HTTP API](https://github.com/craftcms/cms/tree/main/src/controllers).
+This is not a comprehensive list! We have selected a few actions to illustrate fundamentals that many projects can benefit from—and to get you prepared to explore the rest of Craft’s [HTTP API](repo:craftcms/cms/tree/4.x/src/controllers).
 
 Action | Description
 ------ | -----------

docs/4.x/extend/element-types.md

@@ -456,7 +456,7 @@ Event::on(
 );
 ```
 
-`mandatory` here means that the layout element _must_ be present in the field layout, not that a value is required. Take a look at the existing [field layout element types](repo:craftcms/cms/tree/main/src/fieldlayoutelements) to see which makes the most sense for your attribute.
+`mandatory` here means that the layout element _must_ be present in the field layout, not that a value is required. Take a look at the existing [field layout element types](repo:craftcms/cms/tree/4.x/src/fieldlayoutelements) to see which makes the most sense for your attribute.
 
 ::: tip
 Despite basing our `price` layout element on <craft4:craft\fieldlayoutelements\TextField>, the class is deceptively well-suited for customization. Here, we’ve begun to transform it into a `number` input.

docs/4.x/extend/extending-twig.md

@@ -147,5 +147,5 @@ public function init()
 The `getIsSiteRequest()` check is optional. If your extension provides features that will be useful in system emails (commonly triggered from the control panel), or will be used when rendering templates from console requests (less common, but still valid), you may want to register it in all contexts.
 
 ::: tip
-We’ve only covered the simplest means of extending the Twig environment—you can also provide custom _tags_ or _operators_. Craft’s own [Twig extension](https://github.com/craftcms/cms/tree/main/src/web/twig) is a great place to look for examples of advanced features.
+We’ve only covered the simplest means of extending the Twig environment—you can also provide custom _tags_ or _operators_. Craft’s own [Twig extension](repo:craftcms/cms/tree/4.x/src/web/twig) is a great place to look for examples of advanced features.
 :::

docs/4.x/extend/graphql.md

@@ -23,18 +23,18 @@ Craft relies on the [webonyx/graphql-php](https://github.com/webonyx/graphql-php
 Be mindful of Craft vs. GraphQL terminology, because there are overlapping terms that can be confusing. It helps to pay careful attention to namespacing when looking at code examples.
 :::
 
-The rest of this page will cover each of the main things you may need to work with. If you’d like some concrete examples, have a look at Craft’s own pieces in the [`src/gql/` directory](https://github.com/craftcms/cms/tree/main/src/gql).
+The rest of this page will cover each of the main things you may need to work with. If you’d like some concrete examples, have a look at Craft’s own pieces in the [`src/gql/` directory](repo:craftcms/cms/tree/4.x/src/gql).
 
 ### Limitations
 
 If you’re planning advanced or elaborate GraphQL features, please be aware of the following limitations with Craft’s GraphQL implementation:
 
 - GraphQL subscriptions aren’t currently supported.
-- Advanced query builder functions [are not exposed for GraphQL](https://github.com/craftcms/cms/issues/7842).
+- Advanced query builder functions [are not exposed for GraphQL](repo:craftcms/cms/issues/7842).
 
 ## Folder Structure
 
-Here’s a high-level look at the folder structure we’ll explore in our example adding a “Widget” element. You can structure things however you want, we’re just following [Craft’s organization](https://github.com/craftcms/cms/tree/main/src/gql):
+Here’s a high-level look at the folder structure we’ll explore in our example adding a “Widget” element. You can structure things however you want, we’re just following [Craft’s organization](repo:craftcms/cms/tree/4.x/src/gql):
 
 ```treeview
 src/gql/

docs/4.x/extend/module-guide.md

@@ -14,7 +14,7 @@ Namespace
 
 Module ID
 : Something that uniquely identifies the module within your project. IDs must begin with a letter and contain only lowercase letters, numbers, and dashes, and should be `kebab-cased`.
-: The module ID will become the first segment in [controller action](./controllers.md) paths. Avoid names that will conflict with Craft’s core [controllers](repo:craftcms/cms/tree/develop/src/controllers) or the handles of any installed plugins (e.g. `app` would conflict with <craft4:craft\controllers\AppController>, and `commerce` would collide with [Commerce](../../commerce/4.x/README.md)).
+: The module ID will become the first segment in [controller action](./controllers.md) paths. Avoid names that will conflict with Craft’s core [controllers](repo:craftcms/cms/tree/4.x/src/controllers) or the handles of any installed plugins (e.g. `app` would conflict with <craft4:craft\controllers\AppController>, and `commerce` would collide with [Commerce](../../commerce/4.x/README.md)).
 
 
 As an alternative to modules, private [plugins](plugin-guide.md) <Since ver="4.4.0" feature="Private plugins" /> provide all the functionality of a regular plugin, but are intended to be tracked as part of a project rather than distributed.