diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 5bb29ab50e..9f4da5dab8 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,6 +1,6 @@ Specify library name and version: **lib/1.0** -- [ ] I've read the [guidelines](https://github.com/conan-io/conan-center-index/wiki#how-to-submit-a-pull-request) for contributing. +- [ ] I've read the [guidelines](https://github.com/conan-io/conan-center-index/blob/master/docs/how_to_add_packages.mdt) for contributing. - [ ] I've followed the [PEP8](https://www.python.org/dev/peps/pep-0008/) style guides for Python code in the recipes. - [ ] I've used the [latest](https://github.com/conan-io/conan/releases/latest) Conan client version. - [ ] I've tried at least one configuration locally with the diff --git a/docs/error_knowledge_base.md b/docs/error_knowledge_base.md index 7fe9253ba6..59724ec393 100644 --- a/docs/error_knowledge_base.md +++ b/docs/error_knowledge_base.md @@ -156,7 +156,7 @@ class SomeRecipe(ConanFile): exports = "LICENSE.md" # not allowed ``` -There is a complete explanation in the [FAQ](https://github.com/conan-io/conan-center-index/wiki/FAQ#should-recipes-export-a-recipes-license). +There is a complete explanation in the [FAQ](faqs.md#should-recipes-export-a-recipes-license). #### **#KB-H024: "TEST PACKAGE FOLDER"** diff --git a/docs/faqs.md b/docs/faqs.md index 2cdff62c53..b55a60f224 100644 --- a/docs/faqs.md +++ b/docs/faqs.md @@ -74,7 +74,7 @@ Currently, the Jenkins orchestration library for this build service is not avail ## Why not x86 binaries? -As described in the [Supported platforms and configurations](https://github.com/conan-io/conan-center-index/wiki/Supported-Platforms-And-Configurations), only the x86_64 architecture is available for download, the rest must be built from sources. The reasons behind this decision are: +As described in the [Supported platforms and configurations](supported_platforms_and_configurations.md), only the x86_64 architecture is available for download, the rest must be built from sources. The reasons behind this decision are: * Few users need different pre-built packages that are not x86_64 packages, this number is less than 10% of total users (data obtained through the download counter from Bintray), and tends to decrease over the years; * Some OS are putting the x86 as obsolete, examples [macOS](https://developer.apple.com/documentation/macos-release-notes/macos-catalina-10_15-release-notes) and Ubuntu 20.04; diff --git a/docs/how_to_add_packages.md b/docs/how_to_add_packages.md index dd9d31a346..ac869c036e 100644 --- a/docs/how_to_add_packages.md +++ b/docs/how_to_add_packages.md @@ -18,7 +18,7 @@ When the pull request is reviewed and merged, those packages are published to ce The [conan-center-index](https://github.com/conan-io/conan-center-index) (this repository) contains recipes for the [conan-center](https://bintray.com/conan/conan-center) repository. -To contribute with a Conan recipe into the `conan-center` repository you can submit a [Pull Request](https://github.com/conan-io/conan-center-index/pulls) to the **master branch** of this repository. The connected **continuous integration system** will generate binary packages automatically for the most common platforms and compilers. See [the Supported Platforms and Configurations page](https://github.com/conan-io/conan-center-index/wiki/Supported-Platforms-And-Configurations) to know the generated configurations. For a C++ library, the system is currently generating more than 100 binary packages. +To contribute with a Conan recipe into the `conan-center` repository you can submit a [Pull Request](https://github.com/conan-io/conan-center-index/pulls) to the **master branch** of this repository. The connected **continuous integration system** will generate binary packages automatically for the most common platforms and compilers. See [the Supported Platforms and Configurations page](supported_platforms_and_configurations.md) to know the generated configurations. For a C++ library, the system is currently generating more than 100 binary packages. > ⚠️ **Note**: This CI service is not a testing service, it is a binary building service for package **releases**. Unit tests shouldn't be built nor ran in recipes by default. Before submitting a PR it is mandatory to run at least a local package creation. @@ -149,4 +149,4 @@ Call `conan create . lib/1.0@` in the folder of the recipe using the profile you ### Debugging failed builds - Go to the [Error Knowledge Base](https://github.com/conan-io/conan-center-index/wiki/Error-Knowledge-Base) page to know more. + Go to the [Error Knowledge Base](error_knowledge_base.md) page to know more.