Remove outdated CodeTour files

[cgoldberg]

User description

💥 What does this PR do?

This PR removes the /.tours directory and the 2 .tour files it contains. These are for use with the CodeTour extension for VSCode to provide a walkthrough of a codebase. There is one for Bazel and one for Python. Both are outdated and reference areas of code that have moved or no longer exist.

🔄 Types of changes

• Cleanup (formatting, renaming)

---

PR Type

Other

---

Description

• Removes outdated CodeTour extension files

• Deletes .tours/bazel.tour and .tours/building-and-testing-the-python-bindings.tour

• Files referenced outdated code locations and structure

---

Diagram Walkthrough

flowchart LR
  A[".tours directory"] -- "contains outdated tours" --> B["bazel.tour"]
  A -- "contains outdated tours" --> C["building-and-testing-the-python-bindings.tour"]
  B -- "deleted" --> D["Removed"]
  C -- "deleted" --> D

Loading

File Walkthrough

Relevant files

Cleanup

bazel.tour Delete outdated Bazel CodeTour file                                            .tours/bazel.tour Deleted entire file containing CodeTour walkthrough for Bazel File contained 22 lines with steps referencing WORKSPACE and BUILD.bazel Tour was outdated and referenced code areas no longer in use +0/-22    building-and-testing-the-python-bindings.tour Delete outdated Python bindings CodeTour file                        .tours/building-and-testing-the-python-bindings.tour Deleted entire file containing CodeTour walkthrough for Python bindings File contained 47 lines with steps referencing py/BUILD.bazel targets Tour was outdated with references to code structure that has changed +0/-47

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.