From 12b084d4eb5c3d3364d2e3208a73d74a0f85898c Mon Sep 17 00:00:00 2001 From: Lilith Orion Hafner Date: Wed, 28 Feb 2024 19:17:21 +0000 Subject: [PATCH 1/3] Update package naming guidelines link in CONTRIBUTING.md The new link is unstable, but at least it's not broken. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 69f59d5e5952b5b..050dce01d8b429f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,7 +8,7 @@ You can register your package! See [Registering a package in General](https://github.com/JuliaRegistries/General#registering-a-package-in-general) in the README for how to do that. The "FAQ" section in the README helps answer many more questions, like [do I need to register a package to install it?](https://github.com/JuliaRegistries/General#do-i-need-to-register-a-package-to-install-it), [should I register my package?](https://github.com/JuliaRegistries/General#should-i-register-my-package), and more. -* Please be aware of the [package naming guidelines](https://pkgdocs.julialang.org/dev/creating-packages/#Package-naming-guidelines-1) +* Please be aware of the [package naming guidelines](https://docs.julialang.org/en/v1.12-dev/tutorials/creating-packages/#Package-naming-guidelines) * We strongly encourage authors to follow best practices like having documentation (or a descriptive README), tests, and continuous integration. ## As a Julia community member From 1d06337fe00a401e8f7c2a5d8449a05b8a508fad Mon Sep 17 00:00:00 2001 From: Lilith Orion Hafner Date: Mon, 1 Apr 2024 19:54:40 +0000 Subject: [PATCH 2/3] Update URL for the "guidelines" => "rules" PR --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 050dce01d8b429f..afae32e0e17d4c5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,7 +8,7 @@ You can register your package! See [Registering a package in General](https://github.com/JuliaRegistries/General#registering-a-package-in-general) in the README for how to do that. The "FAQ" section in the README helps answer many more questions, like [do I need to register a package to install it?](https://github.com/JuliaRegistries/General#do-i-need-to-register-a-package-to-install-it), [should I register my package?](https://github.com/JuliaRegistries/General#should-i-register-my-package), and more. -* Please be aware of the [package naming guidelines](https://docs.julialang.org/en/v1.12-dev/tutorials/creating-packages/#Package-naming-guidelines) +* Please be aware of the [package naming guidelines](https://docs.julialang.org/en/v1.12-dev/tutorials/creating-packages/#Package-naming-rules) * We strongly encourage authors to follow best practices like having documentation (or a descriptive README), tests, and continuous integration. ## As a Julia community member From 3022355ed1981cef45e7d7ca6b89797b9c55e696 Mon Sep 17 00:00:00 2001 From: Lilith Orion Hafner Date: Mon, 1 Apr 2024 20:24:22 +0000 Subject: [PATCH 3/3] Yet another URL --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index afae32e0e17d4c5..693898064c72a5e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,7 +8,7 @@ You can register your package! See [Registering a package in General](https://github.com/JuliaRegistries/General#registering-a-package-in-general) in the README for how to do that. The "FAQ" section in the README helps answer many more questions, like [do I need to register a package to install it?](https://github.com/JuliaRegistries/General#do-i-need-to-register-a-package-to-install-it), [should I register my package?](https://github.com/JuliaRegistries/General#should-i-register-my-package), and more. -* Please be aware of the [package naming guidelines](https://docs.julialang.org/en/v1.12-dev/tutorials/creating-packages/#Package-naming-rules) +* Please be aware of the [package naming guidelines](https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines) * We strongly encourage authors to follow best practices like having documentation (or a descriptive README), tests, and continuous integration. ## As a Julia community member