Move docs/sdk_developers/changelog_entry.md, checklist.md, merge_conflicts.md, signing.md, testing.md todocs/sdk_developers/training/workflow

Author: pratyush0325

.github/ISSUE_TEMPLATE/01_good_first_issue.yml

@@ -229,8 +229,8 @@ body:
         EDIT OR EXPAND THE CHECKLIST ON WHAT IS REQUIRED TO BE ABLE TO MERGE A PULL REQUEST FOR THIS ISSUE
       value: |
         To be able to merge a pull request for this issue, we need:
-        - [ ] **Changelog Entry:** Correct changelog entry (please link to the documentation - [see guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/changelog_entry.md))
-        - [ ] **Signed commits:** commits must be DCO and GPG key signed ([see guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/signing.md))
+        - [ ] **Changelog Entry:** Correct changelog entry (please link to the documentation - [see guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/changelog_entry.md))
+        - [ ] **Signed commits:** commits must be DCO and GPG key signed ([see guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/signing.md))
         - [ ] **All Tests Pass:** our workflow checks like unit and integration tests must pass
         - [ ] **Issue is Solved:** The implementation fully addresses the issue requirements as described above
         - [ ] **No Further Changes are Made:** Code review feedback has been addressed and no further changes are requested
@@ -248,8 +248,8 @@ body:
         - [ ] **Claim this issue:** Comment below that you are interested in working on the issue. Without assignment, your pull requests might be closed and the issue given to another developer.
         - [ ] **Wait for assignment:** A community member with the given rights will add you as an assignee of the issue
         - [ ] **Fork, Branch and Work on the issue:** Create a copy of the repository, create a branch for the issue and solve the problem. For instructions, please read our [Contributing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/CONTRIBUTING.md) file. Further help can be found at [Set-up Training](https://github.com/hiero-ledger/hiero-sdk-python/tree/main/docs/sdk_developers/training/setup) and [Workflow Training](https://github.com/hiero-ledger/hiero-sdk-python/tree/main/docs/sdk_developers/training/workflow).
-        - [ ] **DCO and GPG key sign each commit :** each commit must be -s and -S signed. An explanation on how to do this is at [Signing Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/signing.md)
-        - [ ] **Add a Changelog Entry :** your pull request will require a changelog. Read [Changelog Entry Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/changelog_entry.md) to learn how.
+        - [ ] **DCO and GPG key sign each commit :** each commit must be -s and -S signed. An explanation on how to do this is at [Signing Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/signing.md)
+        - [ ] **Add a Changelog Entry :** your pull request will require a changelog. Read [Changelog Entry Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/changelog_entry.md) to learn how.
         - [ ] **Push and Create a Pull Request :** Once your issue is resolved, and your commits are signed, and you have a changelog entry, push your changes and create a pull request. Detailed instructions can be found at [Submit PR Training](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/11_submit_pull_request.md), part of [Workflow Training](https://github.com/hiero-ledger/hiero-sdk-python/tree/main/docs/sdk_developers/training/workflow).
         - [ ] **You did it 🎉:** A maintainer or committer will review your pull request and provide feedback. If approved, we will merge the fix in the main branch. Thanks for being part of the Hiero community as an open-source contributor ❤️
 

.github/ISSUE_TEMPLATE/04_good_first_issue_candidate.yml

@@ -238,7 +238,7 @@ body:
       value: |
         To be able to merge a pull request for this issue, we need:
         - [ ] **Changelog Entry:** Correct changelog entry (please link to the documentation - [see guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/changelog_entry.md))
-        - [ ] **Signed commits:** commits must be DCO and GPG key signed ([see guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/signing.md))
+        - [ ] **Signed commits:** commits must be DCO and GPG key signed ([see guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/signing.md))
         - [ ] **All Tests Pass:** our workflow checks like unit and integration tests must pass
         - [ ] **Issue is Solved:** The implementation fully addresses the issue requirements as described above
         - [ ] **No Further Changes are Made:** Code review feedback has been addressed and no further changes are requested
@@ -256,8 +256,8 @@ body:
         - [ ] **Claim this issue:** Comment below that you are interested in working on the issue. Without assignment, your pull requests might be closed and the issue given to another developer.
         - [ ] **Wait for assignment:** A community member with the given rights will add you as an assignee of the issue
         - [ ] **Fork, Branch and Work on the issue:** Create a copy of the repository, create a branch for the issue and solve the problem. For instructions, please read our [Contributing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/CONTRIBUTING.md) file. Further help can be found at [Set-up Training](https://github.com/hiero-ledger/hiero-sdk-python/tree/main/docs/sdk_developers/training/setup) and [Workflow Training](https://github.com/hiero-ledger/hiero-sdk-python/tree/main/docs/sdk_developers/training/workflow).
-        - [ ] **DCO and GPG key sign each commit :** each commit must be -s and -S signed. An explanation on how to do this is at [Signing Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/signing.md)
-        - [ ] **Add a Changelog Entry :** your pull request will require a changelog. Read [Changelog Entry Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/changelog_entry.md) to learn how.
+        - [ ] **DCO and GPG key sign each commit :** each commit must be -s and -S signed. An explanation on how to do this is at [Signing Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/signing.md)
+        - [ ] **Add a Changelog Entry :** your pull request will require a changelog. Read [Changelog Entry Guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/changelog_entry.md) to learn how.
         - [ ] **Push and Create a Pull Request :** Once your issue is resolved, and your commits are signed, and you have a changelog entry, push your changes and create a pull request. Detailed instructions can be found at [Submit PR Training](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/11_submit_pull_request.md), part of [Workflow Training](https://github.com/hiero-ledger/hiero-sdk-python/tree/main/docs/sdk_developers/training/workflow).
         - [ ] **You did it 🎉:** A maintainer or committer will review your pull request and provide feedback. If approved, we will merge the fix in the main branch. Thanks for being part of the Hiero community as an open-source contributor ❤️
 

.github/workflows/bot-merge-conflict.yml

@@ -53,7 +53,7 @@ jobs:
             Please resolve these conflicts locally and push the changes.
 
             To assist you, please read:
-            - [Resolving Merge Conflicts](docs/sdk_developers/merge_conflicts.md)
+            - [Resolving Merge Conflicts](docs/sdk_developers/training/workflow/merge_conflicts.md)
             - [Rebasing Guide](docs/sdk_developers/rebasing.md)
 
             Thank you for contributing!

.github/workflows/bot-verified-commits.yml

@@ -53,7 +53,7 @@ jobs:
             View your commit verification status: [Commits Tab]($COMMITS_URL).
 
             To achieve verified status, please read:
-            - [Signing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/signing.md)
+            - [Signing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/signing.md)
             - [README](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/README.md)
             - [Discord](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/discord.md)
 

.github/workflows/bot-workflows.yml

@@ -50,11 +50,11 @@ jobs:
           Your pull request cannot be merged as it is not passing all our workflow checks. 
           Please click on each check to review the logs and resolve issues so all checks pass.
           To help you:
-          - [DCO signing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/signing.md)
-          - [Changelog guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/changelog_entry.md)
-          - [Merge conflicts guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/merge_conflicts.md)
+          - [DCO signing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/signing.md)
+          - [Changelog guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/changelog_entry.md)
+          - [Merge conflicts guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/merge_conflicts.md)
           - [Rebase guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/rebasing.md)
-          - [Testing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/testing.md)
+          - [Testing guide](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/sdk_developers/training/workflow/testing.md)
           - [Discord](https://github.com/hiero-ledger/hiero-sdk-python/blob/main/docs/discord.md)
           - [Community Calls](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week)
           Thank you for contributing!

CHANGELOG.md

@@ -679,7 +679,7 @@ contract_call_local_pb2.ContractLoginfo -> contract_types_pb2.ContractLoginfo
 
 ### Changed
 
-- N/A
+- Move docs/sdk_developers/changelog_entry.md, checklist.md, merge_conflicts.md, signing.md, testing.md to docs/sdk_developers/training/workflow
 
 ### Fixed
 

CONTRIBUTING.md

@@ -29,10 +29,10 @@ Thank you for your interest in contributing to the Hiero Python SDK!
 4. Submit a PR
 
 **Requirements:**
-- Signed commits (GPG + DCO) - [Signing Guide](docs/sdk_developers/signing.md)
-- Updated changelog - [Changelog Guide](docs/sdk_developers/changelog_entry.md)
+- Signed commits (GPG + DCO) - [Signing Guide](docs/sdk_developers/training/workflow/signing.md)
+- Updated changelog - [Changelog Guide](docs/sdk_developers/training/workflow/changelog_entry.md)
 - Tests pass
-- Code quality checks - [Checklist](docs/sdk_developers/checklist.md)
+- Code quality checks - [Checklist](docs/sdk_developers/training/workflow/checklist.md)
 
 
 #### ⚠️ A Note on Breaking Changes
@@ -94,11 +94,11 @@ We welcome blog posts! Whether you're sharing a tutorial, case study, or your ex
 |-------|----------------|
 | [Setup](docs/sdk_developers/setup.md) | Fork, clone, install, configure |
 | [Workflow](docs/sdk_developers/workflow.md) | Branching, committing, PRs |
-| [Signing](docs/sdk_developers/signing.md) | GPG + DCO commit signing |
-| [Changelog](docs/sdk_developers/changelog_entry.md) | Writing changelog entries |
-| [Checklist](docs/sdk_developers/checklist.md) | Pre-submission checklist |
+| [Signing](docs/sdk_developers/training/workflow/signing.md) | GPG + DCO commit signing |
+| [Changelog](docs/sdk_developers/training/workflow/changelog_entry.md) | Writing changelog entries |
+| [Checklist](docs/sdk_developers/training/workflow/checklist.md) | Pre-submission checklist |
 | [Rebasing](docs/sdk_developers/rebasing.md) | Keeping branch updated |
-| [Merge Conflicts](docs/sdk_developers/merge_conflicts.md) | Resolving conflicts |
+| [Merge Conflicts](docs/sdk_developers/training/workflow/merge_conflicts.md) | Resolving conflicts |
 | [Types](docs/sdk_developers/types.md) | Python type hints |
 | [Linting](docs/sdk_developers/linting.md) | Code quality tools |
 

README.md

@@ -64,10 +64,10 @@ print(f"Balance: {balance.hbars} HBAR")
 - **[Contributing Guide](CONTRIBUTING.md)** - Start here!
 - **[Setup Guide](docs/sdk_developers/setup.md)** - First-time environment setup
 - **[Workflow Guide](docs/sdk_developers/workflow.md)** - Day-to-day development workflow
-- **[Signing Guide](docs/sdk_developers/signing.md)** - GPG and DCO commit signing (required)
-- **[Changelog Guide](docs/sdk_developers/changelog_entry.md)** - How to write changelog entries
+- **[Signing Guide](docs/sdk_developers/training/workflow/signing.md)** - GPG and DCO commit signing (required)
+- **[Changelog Guide](docs/sdk_developers/training/workflow/changelog_entry.md)** - How to write changelog entries
 - **[Rebasing Guide](docs/sdk_developers/rebasing.md)** - Keep your branch up-to-date
-- **[Merge Conflicts Guide](docs/sdk_developers/merge_conflicts.md)** - Resolve conflicts
+- **[Merge Conflicts Guide](docs/sdk_developers/training/workflow/merge_conflicts.md)** - Resolve conflicts
 - **[Typing Guide](docs/sdk_developers/types.md)** - Python type hints
 - **[Linting Guide](docs/sdk_developers/linting.md)** - Code quality tools
 

docs/maintainers/good_first_issue_candidate_guidelines.md

@@ -194,6 +194,6 @@ A candidate should be promoted to a full **Good First Issue** when:
 
 - [Good First Issue Guidelines](./good_first_issues_guidelines.md) — what qualifies as a GFI
 - [Contributing Guide](../../CONTRIBUTING.md) — how to contribute
-- [DCO Signing Guide](../sdk_developers/signing.md) — commit signing requirements
+- [DCO Signing Guide](../sdk_developers/training/workflow/signing.md) — commit signing requirements
 - [Discord Community](../discord.md) — get help from the community
 - [Community Calls](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week) — weekly office hours

docs/maintainers/good_first_issues_guidelines.md

@@ -243,7 +243,7 @@ When evaluating whether to label an issue as a Good First Issue, consider:
 ## Additional Resources
 
 - [Contributing Guide](../../CONTRIBUTING.md)
-- [DCO Signing Guide](../sdk_developers/signing.md)
-- [Changelog Entry Guide](../sdk_developers/changelog_entry.md)
+- [DCO Signing Guide](../sdk_developers/workflow/training/signing.md)
+- [Changelog Entry Guide](../sdk_developers/workflow/training/changelog_entry.md)
 - [Discord Community](../discord.md)
 - [Community Calls](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week)