From 3d17182f5a6d62856f4c334c977a4f678ba6e549 Mon Sep 17 00:00:00 2001 From: GarmashAlex Date: Fri, 9 May 2025 15:41:55 +0300 Subject: [PATCH 1/3] fix dead link --- contrib/CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/CONTRIBUTING.md b/contrib/CONTRIBUTING.md index e0a0a75cee..31006caae1 100644 --- a/contrib/CONTRIBUTING.md +++ b/contrib/CONTRIBUTING.md @@ -102,7 +102,7 @@ Patchsets and enhancements should always be focused. A pull request could add a Specifically, pull requests must adhere to the following criteria: - **Must** branch off from `staging`. Make sure that all your PRs are using `staging` branch as a base or will be closed. - Contain fewer than 50 files. PRs with more than 50 files will be closed. -- Use the specific [template](./.github/pull_request_template.md) appropriate to your contribution. +- Use the specific [template](https://github.com/opentensor/bittensor/blob/master/.github/pull_request_template.md) appropriate to your contribution. - If a PR introduces a new feature, it *must* include corresponding tests. - Other PRs (bug fixes, refactoring, etc.) should ideally also have tests, as they provide proof of concept and prevent regression. - Categorize your PR properly by using GitHub labels. This aids in the review process by informing reviewers about the type of change at a glance. @@ -127,7 +127,7 @@ Please follow these steps to have your contribution considered by the maintainer 1. Read the [development workflow](./DEVELOPMENT_WORKFLOW.md) defined for this repository to understand our workflow. 2. Ensure your PR meets the criteria stated in the 'Pull Request Philosophy' section. 3. Include relevant tests for any fixed bugs or new features as stated in the [testing guide](./TESTING.md). -4. Follow all instructions in [the template](https://github.com/opentensor/bittensor/blob/master/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md) to create the PR. +4. Follow all instructions in [the template](https://github.com/opentensor/bittensor/blob/master/.github/pull_request_template.md) to create the PR. 5. Ensure your commit messages are clear and concise. Include the issue number if applicable. 6. If you have multiple commits, rebase them into a single commit using `git rebase -i`. 7. Explain what your changes do and why you think they should be merged in the PR description consistent with the [style guide](./STYLE.md). From 2d04c3966f26b0ac1f7a86ad290226bfef06b415 Mon Sep 17 00:00:00 2001 From: GarmashAlex Date: Fri, 9 May 2025 18:40:17 +0300 Subject: [PATCH 2/3] Update contrib/CONTRIBUTING.md Co-authored-by: BD Himes <37844818+thewhaleking@users.noreply.github.com> --- contrib/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/CONTRIBUTING.md b/contrib/CONTRIBUTING.md index 31006caae1..79ca1e7bb4 100644 --- a/contrib/CONTRIBUTING.md +++ b/contrib/CONTRIBUTING.md @@ -102,7 +102,7 @@ Patchsets and enhancements should always be focused. A pull request could add a Specifically, pull requests must adhere to the following criteria: - **Must** branch off from `staging`. Make sure that all your PRs are using `staging` branch as a base or will be closed. - Contain fewer than 50 files. PRs with more than 50 files will be closed. -- Use the specific [template](https://github.com/opentensor/bittensor/blob/master/.github/pull_request_template.md) appropriate to your contribution. +- Use the specific [template](../.github/pull_request_template.md) appropriate to your contribution. - If a PR introduces a new feature, it *must* include corresponding tests. - Other PRs (bug fixes, refactoring, etc.) should ideally also have tests, as they provide proof of concept and prevent regression. - Categorize your PR properly by using GitHub labels. This aids in the review process by informing reviewers about the type of change at a glance. From de54deaf2654c800eee98a5f18e4c9c06f49b7d6 Mon Sep 17 00:00:00 2001 From: GarmashAlex Date: Fri, 9 May 2025 18:40:24 +0300 Subject: [PATCH 3/3] Update contrib/CONTRIBUTING.md Co-authored-by: BD Himes <37844818+thewhaleking@users.noreply.github.com> --- contrib/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/CONTRIBUTING.md b/contrib/CONTRIBUTING.md index 79ca1e7bb4..714102bfd2 100644 --- a/contrib/CONTRIBUTING.md +++ b/contrib/CONTRIBUTING.md @@ -127,7 +127,7 @@ Please follow these steps to have your contribution considered by the maintainer 1. Read the [development workflow](./DEVELOPMENT_WORKFLOW.md) defined for this repository to understand our workflow. 2. Ensure your PR meets the criteria stated in the 'Pull Request Philosophy' section. 3. Include relevant tests for any fixed bugs or new features as stated in the [testing guide](./TESTING.md). -4. Follow all instructions in [the template](https://github.com/opentensor/bittensor/blob/master/.github/pull_request_template.md) to create the PR. +4. Follow all instructions in [the template](../.github/pull_request_template.md) to create the PR. 5. Ensure your commit messages are clear and concise. Include the issue number if applicable. 6. If you have multiple commits, rebase them into a single commit using `git rebase -i`. 7. Explain what your changes do and why you think they should be merged in the PR description consistent with the [style guide](./STYLE.md).