Improved testing of git refs in documentation #291
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…273 Changes in file docs/utils.py: - improved validation slightly - added new doctest for changes
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (3)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughThe pull request focuses on improving the Git reference validation logic in the Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
|
Here's the code health analysis summary for commits Analysis Summary
|
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
reactive-firewall
temporarily deployed
to
Experimenting
GitHub Actions
Inactive
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
docs/utils.py(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/utils.py (2)
Pattern **/*.py: When reviewing Python code for this project: 1. Prioritize portability over clarity, especially when dealing with cross-Python
compatibility. However, with the priority in mind, do still consider improvements to
clarity when relevant.
2. As a general guideline, consider the code style advocated in the PEP 8 standard
(excluding the use of spaces for indentation) and evaluate suggested changes for code
style compliance.
3. As a style convention, consider the code style advocated in
CEP-8
and evaluate suggested changes for code style compliance.
4. As a general guideline, try to provide any relevant, official, and supporting
documentation links to any tool's suggestions in review comments. This guideline is
important for posterity.
5. As a general rule, undocumented function definitions and class definitions in the
project's Python code are assumed incomplete. Please consider suggesting a short
summary of the code for any of these incomplete definitions as docstrings when
reviewing. All documentation including docstrings in the project are to align with
the guidelines set by
CEP-7.
6. Verify Flake8's configuration file is located at ".flake8.ini". Flake8 is run
automaticly by the flake8-cq GHA used by the .github/workflows/flake8.yml workflow.
7. Verify alignment of any new changes, with the code style advocated in
CEP-8,
pointing out any introduced deviations.
Pattern docs/*: When a project contains a docs/ directory: 1. Consider the files in the docs/ directory tree the core/main/in-depth documentation
of the project. Also consider the 'docs/**.md' files the second place to look for
project documentation after the 'README.md' file.
2. When reviewing the documentation files (e.g. docs/**.md), they should additionally
be linted with help from the tool markdownlint, pointing out any issues.
3. When reviewing the documentation files in docs/ directory, they should additionally
be linted with help from the tool languagetool, pointing out any issues.
📓 Learnings (1)
📓 Common learnings
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-12-12T20:51:15.319Z
Learning: In the multicast project, when refactoring shell scripts, prefer improving organization within a single file over splitting into multiple files, unless the benefits of modularity clearly outweigh the added complexity in security, permissions, and debugging.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-11-12T10:29:50.461Z
Learning: For future scripts, reactive-firewall prefers to use only POSIX built-ins (like `printf` instead of `echo`) to align with CEP-8 conventions.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-11-21T02:05:08.096Z
Learning: Reactive-firewall prefers to specify the full raw URL when fetching files from gists to ensure correct retrieval of content, particularly when the file is in markdown format.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-11-12T10:29:55.563Z
Learning: For future scripts, reactive-firewall prefers to keep the shebang line with an extra space (e.g., `#! /bin/bash`) as per project style.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#184
File: LICENSE.md:36-43
Timestamp: 2024-11-14T07:03:35.207Z
Learning: Reactive-firewall prefers that I verify URLs before suggesting changes, and avoid raising hypothetical issues without verification.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#235
File: .github/workflows/makefile-lint.yml:41-52
Timestamp: 2024-12-06T08:21:21.876Z
Learning: Reactive-firewall prefers to suppress errors in `apt-get install` commands when individual checks of the installed packages are performed afterwards, to allow for more granular error handling.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-12-13T01:44:13.412Z
Learning: In the multicast project's shell scripts, prefer organizing code into logical sections with clear comments (e.g., "=== Environment Setup ===") to maintain readability and maintainability while keeping related functions together.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#184
File: tests/check_pip:259-265
Timestamp: 2024-11-15T19:32:16.878Z
Learning: Reactive-firewall prefers that code changes adhere to SOLID design principles, specifically avoiding unnecessary complexity (AHA principle), maintaining the Single Responsibility Principle, and ensuring complex work is done on separate development branches (Open/Closed Principle).
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#110
File: docs/USAGE.md:66-66
Timestamp: 2024-11-12T10:29:55.563Z
Learning: Reactive-firewall prefers to use "Caveat" as a heading instead of "Caution".
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-10-08T03:15:05.171Z
Learning: For future reviews, remember that when drafting or updating CEP (Convention Enhancement Proposal) documents, it's important to adhere to the project's standard format and include all relevant sections such as Motivation, Detailed Explanation, Implementation Guidelines, Impact, and References.
🔇 Additional comments (1)
docs/utils.py (1)
61-66: Well-structured doctest for Git reference validation!The new test case effectively validates the rejection of references containing consecutive dots, which aligns with Git's reference naming conventions.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
reactive-firewall
temporarily deployed
to
Testing
GitHub Actions
Inactive
Changes in file docs/utils.py: - use only tabs for indentation
reactive-firewall
temporarily deployed
to
Testing
GitHub Actions
Inactive
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
def _validate_git_ref(ref: str) -> str:
reactive-firewall
added
documentation
Changes in file docs/utils.py: Unknown Changes
reactive-firewall
temporarily deployed
to
Testing
GitHub Actions
Inactive
reactive-firewall
changed the title
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
docs/utils.py(2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/utils.py (2)
Pattern **/*.py: When reviewing Python code for this project: 1. Prioritize portability over clarity, especially when dealing with cross-Python
compatibility. However, with the priority in mind, do still consider improvements to
clarity when relevant.
2. As a general guideline, consider the code style advocated in the PEP 8 standard
(excluding the use of spaces for indentation) and evaluate suggested changes for code
style compliance.
3. As a style convention, consider the code style advocated in
CEP-8
and evaluate suggested changes for code style compliance.
4. As a general guideline, try to provide any relevant, official, and supporting
documentation links to any tool's suggestions in review comments. This guideline is
important for posterity.
5. As a general rule, undocumented function definitions and class definitions in the
project's Python code are assumed incomplete. Please consider suggesting a short
summary of the code for any of these incomplete definitions as docstrings when
reviewing. All documentation including docstrings in the project are to align with
the guidelines set by
CEP-7.
6. Verify Flake8's configuration file is located at ".flake8.ini". Flake8 is run
automaticly by the flake8-cq GHA used by the .github/workflows/flake8.yml workflow.
7. Verify alignment of any new changes, with the code style advocated in
CEP-8,
pointing out any introduced deviations.
Pattern docs/*: When a project contains a docs/ directory: 1. Consider the files in the docs/ directory tree the core/main/in-depth documentation
of the project. Also consider the 'docs/**.md' files the second place to look for
project documentation after the 'README.md' file.
2. When reviewing the documentation files (e.g. docs/**.md), they should additionally
be linted with help from the tool markdownlint, pointing out any issues.
3. When reviewing the documentation files in docs/ directory, they should additionally
be linted with help from the tool languagetool, pointing out any issues.
📓 Learnings (1)
📓 Common learnings
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-12-12T20:51:15.319Z
Learning: In the multicast project, when refactoring shell scripts, prefer improving organization within a single file over splitting into multiple files, unless the benefits of modularity clearly outweigh the added complexity in security, permissions, and debugging.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-11-12T10:29:50.461Z
Learning: For future scripts, reactive-firewall prefers to use only POSIX built-ins (like `printf` instead of `echo`) to align with CEP-8 conventions.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-11-21T02:05:08.096Z
Learning: Reactive-firewall prefers to specify the full raw URL when fetching files from gists to ensure correct retrieval of content, particularly when the file is in markdown format.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-11-12T10:29:55.563Z
Learning: For future scripts, reactive-firewall prefers to keep the shebang line with an extra space (e.g., `#! /bin/bash`) as per project style.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#184
File: LICENSE.md:36-43
Timestamp: 2024-11-14T07:03:35.207Z
Learning: Reactive-firewall prefers that I verify URLs before suggesting changes, and avoid raising hypothetical issues without verification.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#235
File: .github/workflows/makefile-lint.yml:41-52
Timestamp: 2024-12-06T08:21:21.876Z
Learning: Reactive-firewall prefers to suppress errors in `apt-get install` commands when individual checks of the installed packages are performed afterwards, to allow for more granular error handling.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-12-13T01:44:13.412Z
Learning: In the multicast project's shell scripts, prefer organizing code into logical sections with clear comments (e.g., "=== Environment Setup ===") to maintain readability and maintainability while keeping related functions together.
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#184
File: tests/check_pip:259-265
Timestamp: 2024-11-15T19:32:16.878Z
Learning: Reactive-firewall prefers that code changes adhere to SOLID design principles, specifically avoiding unnecessary complexity (AHA principle), maintaining the Single Responsibility Principle, and ensuring complex work is done on separate development branches (Open/Closed Principle).
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#110
File: docs/USAGE.md:66-66
Timestamp: 2024-11-12T10:29:55.563Z
Learning: Reactive-firewall prefers to use "Caveat" as a heading instead of "Caution".
Learnt from: reactive-firewall
PR: reactive-firewall/multicast#0
File: :0-0
Timestamp: 2024-10-08T03:15:05.171Z
Learning: For future reviews, remember that when drafting or updating CEP (Convention Enhancement Proposal) documents, it's important to adhere to the project's standard format and include all relevant sections such as Motivation, Detailed Explanation, Implementation Guidelines, Impact, and References.
🔇 Additional comments (2)
docs/utils.py (2)
73-78: LGTM! Good test coverage for the consecutive dots validation.The new test case effectively verifies the handling of invalid references containing consecutive dots.
80-80: LGTM! Clean implementation using the extracted pattern.The validation logic correctly uses the new constant and properly checks for consecutive dots.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
reactive-firewall
temporarily deployed
to
Testing
GitHub Actions
Inactive
reactive-firewall
deleted the
patch-enhancing-git-reference-validation-273
branch
23 tasks
This was referenced May 3, 2025
reactive-firewall
added a commit
that referenced
this pull request
May 4, 2025
…bringing together improvements from over 40 previous PRs and addressing over 40 distinct issues. It serves as a comprehensive preparation for future development, establishing strong foundations for the upcoming 2.1 version.
These changes aim to enhance code quality, enforce best practices, and streamline CI/CD processes.
---
- **Files Changed**: 100 files across 10 directories
- **Code Volume**: 4,905 lines added, 1,059 lines deleted
- **Impact Scope**:
- Core Python Files: 8 files (1,370 lines added, 447 lines deleted)
- Documentation: 12 files (425 lines added, 145 lines deleted)
- Configuration: 80 files (3,110+ lines added, ~467 lines deleted)
- **Issue Resolution**: Closes 44+ distinct issues
- **PR Consolidation**: Supersedes 42+ previous PRs
- **Milestone**: Concludes "Pre-Version 2.1 Chores" (milestone/13)
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
- **New Features**
- Introduced extensive static analysis and linting rule configurations for Python and YAML, enforcing documentation, naming conventions, code style, and GitHub Actions workflow patterns.
- Added new GitHub Actions workflows for Flake8 and ShellCheck, and a continuous deployment workflow for PyPI publishing.
- Implemented custom GitHub Actions for artifact management and pip upgrades on Windows.
- Enhanced Makefile with new branding, improved build/install/test targets, and better environment compatibility.
- Added a comprehensive CI/CD output formatting tool for GitHub Actions.
- **Bug Fixes**
- Improved error handling, logging, and validation across core modules (`multicast`, `env`, `exceptions`, `recv`, `hear`, `send`, `skt`).
- Standardized string literals and exception variable naming for clarity and consistency.
- **Documentation**
- Expanded CI and environment configuration documentation, including new badges, usage examples, and copyright/license.
- Improved docstrings, exception guides, and FAQ with clearer examples and error handling.
- **Chores**
- Updated configuration files for coverage, pytest, and dependencies.
- Enhanced `.gitignore` and labeling configuration for better project maintenance.
- Added and updated test scripts and test suite organization for improved coverage and grouping.
- **Style**
- Refactored codebase for consistent string usage, formatting, and logging practices.
- **Tests**
- Reorganized and expanded test suite structure, added dynamic doctest loading, and improved test marker definitions.
- **Refactor**
- Modularized and improved import logic, logging, and internal helper functions for maintainability and robustness.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
1. **Error Handling Improvements**:
- Refactored exception handling for better traceability and maintainability.
- Introduced `ShutdownCommandReceived` exception for explicit shutdown command handling.
2. **Documentation and Templates**:
- Expanded CI and environment configuration documentation, including new badges, usage examples, and copyright/license.
- Improved docstrings, exception guides, and FAQ with clearer examples and error handling.
- Added new tests for Python versions, workflows for minimal acceptance, and doctests.
- Enhanced test suite structure, added dynamic doctest loading, and improved test marker definitions.
1. **Static Analysis and Linting**:
- Introduced extensive static analysis and linting rule configurations for Python and YAML, enforcing documentation, naming conventions, code style, and GitHub Actions workflow patterns.
- Added 20 new AST-grep rules, including 16 multicast-specific, 3 Python-specific, and 1 GHA-specific rules.
2. **Enhanced GitHub Actions**:
- New workflows for **Flake8**, **Shellcheck**, **CD-PyPi**, and **Makefile Lint**.
- Updates to existing workflows for CI, testing, and code quality checks.
- Improved automation for packaging, testing, and deployment.
3. **Housekeeping and Configuration**:
- Revised `.gitignore` to exclude more development artifacts.
- Enhanced `Makefile` with new targets (`branding`, `purge-coverage-artifacts`), dependencies management, and defaults.
- Improved error handling, logging, and validation across core modules (`multicast`, `env`, `exceptions`, `recv`, `hear`, `send`, `skt`).
- Standardized string literals and exception variable naming for clarity and consistency.
- **Removed Legacy Scripts**: Tools like `tool_checkmake.sh` and `tool_shlock_helper.sh` were replaced with symbolic links or moved under `.github/tools/`.
- **Workflow Adjustments**: Deprecated YAML configurations were replaced or updated with streamlined and secure alternatives.
The changes introduced in the `v2.0.8` release (compared to `v2.0.7`) are extensive and cover multiple areas of the repository.
- **Refactoring Exception Handling:**
- Changed exception variable naming from generic (e.g., `err`, `impErr`) to `_cause` for better traceability.
- Improved `raise from` usage to maintain the original exception context.
- Enhanced clarity and maintainability of error handling across the codebase.
**Impact:**
- These changes improve debugging and maintainability by providing more informative and granular error contexts. They also align with best practices for exception handling.
- **`ShutdownCommandReceived` Exception:**
- Added a new exception class to handle shutdown commands explicitly.
- **AST-Grep Rules for Code Standardization:**
- Introduced `.ast-grep` rules to enforce patterns for `doStep` and `setupArgs` implementations.
- Added utility files for Python-specific AST validation.
**Impact:**
- These features enhance robustness by formalizing error handling for shutdown scenarios.
- Enforcing code patterns ensures consistency in the implementation of core functions.
- Updated exception handling examples in `Exception_Guide.md`.
- Revised FAQ and usage documentation to reflect changes in error handling and function signatures.
- Incremented version references in `docs/conf.py`.
**Impact:**
- Documentation is now more accurate and user-friendly, helping developers understand new conventions and best practices.
- **Improved Coverage for Doctests:**
- Added configurations to include only `multicast/*` files in coverage reports for doctests.
- **Additional Test Cases:**
- Added tests for edge cases and regression.
- **Refinements in Test Utilities:**
- Enhanced logging and output formatting using `cioutput.py`.
**Impact:**
- Enhanced test coverage and detailed reporting improve test reliability and debugging efficiency.
- **New PyPI Deployment Workflow:**
- Introduced `CD-PyPi.yml` workflow for automated publishing of releases to PyPI.
- **Updated CI Workflows:**
- Refined CI configurations to align with Python version updates and GitHub Action improvements.
**Impact:**
- The new deployment pipeline automates release publishing, reducing manual overhead.
- Updated CI workflows leverage the latest tools and methodologies, ensuring compatibility and reliability.
- **Consistency Improvements:**
- Unified function type annotations for better static analysis.
- Refactored redundant or deprecated patterns.
- **Tooling Updates:**
- Introduced `.github/tools/cioutput.py` for consistent CI/CD output formatting.
- Enhanced Makefile with branding and improved task definitions.
**Impact:**
- These changes enhance code quality, readability, and maintainability.
- **Deprecations:**
- Removed obsolete shell scripts and replaced them with symbolic links or consolidated versions.
- **Branding:**
- Added branding to the Makefile for a more professional touch.
**Impact:**
- Streamlining and branding improve the overall developer experience and project presentation.
The `v2.0.8` release introduces significant improvements in exception handling, testing, build automation, and code quality. These changes enhance robustness, maintainability, and developer productivity.
- **Branding**: Added branding to the Makefile for a more professional touch.
- **Technical Debt Reduction**: Refactoring legacy code patterns and standardizing coding practices.
This release represents the culmination of numerous smaller efforts, bringing together improvements from over 40 previous PRs and addressing over 40 distinct issues. It serves as a comprehensive preparation for future development, establishing strong foundations for the upcoming 2.1 version.
The PR includes significant improvements to all core modules of the `multicast` package:
- **hear.py**: Substantial refactoring (348 additions, 53 deletions)
- **env.py**: Enhanced environment handling (263 additions, 51 deletions)
- **exceptions.py**: Improved error handling (189 additions, 50 deletions)
- **recv.py**: Optimized receiving functionality (183 additions, 54 deletions)
- **__init__.py**: Updated package initialization (162 additions, 75 deletions)
A major focus on code quality through:
- **20 New AST-grep Rules**: Including 16 multicast-specific, 3 Python-specific, and 1 GHA-specific rules
- **Code Style Standardization**: Consistent string handling and import organization
- **Documentation Requirements**: New rules for enforcing docstrings and test documentation
Comprehensive improvements to build and test infrastructure:
- **11 Workflow Files Updated**: Including 490+ lines of additions
- **New Workflows**: Added dedicated workflows for Flake8, ShellCheck, and PyPI deployment
- **Testing Improvements**: Enhanced pytest configuration (23 lines added)
- **GitHub Actions**: Multiple action upgrades for security and functionality
Significant documentation enhancements:
- **API Documentation**: Improved docstrings across the codebase
- **Usage Guidelines**: Updated USAGE.md, Exception_Guide.md, and FAQ.md
- **CI Documentation**: Added comprehensive CI.md (49 additions)
- **Documentation Tools**: Major improvements to docs/utils.py (216 additions)
This PR demonstrates systematic progression through:
1. **Dependency Maintenance**: 12 dependency updates via Dependabot
2. **Technical Debt Reduction**: Refactoring legacy code patterns
3. **Standardization**: Implementation of consistent coding standards
4. **Automation**: Enhanced testing and CI/CD capabilities
5. **Documentation**: Comprehensive documentation updates reflecting all changes
1. **Code Quality**: Implementation of robust static analysis rules
2. **Developer Experience**: Improved documentation and error handling
3. **Reliability**: Enhanced testing infrastructure and coverage
4. **Maintainability**: Standardized coding patterns and documentation requirements
5. **Build Process**: Streamlined CI/CD workflows with improved caching
> This release represents the culmination of numerous smaller efforts, bringing together improvements from over 40 previous PRs and addressing over 40 distinct issues. It serves as a comprehensive preparation for future development, establishing strong foundations for the upcoming 2.1 version.
>
> These changes aim to enhance code quality, enforce best practices, and streamline CI/CD processes.
- [x] Closes #134
- [x] Closes #135
- [x] Closes #151
- [x] Closes #165
- [x] Closes #171
- [x] Closes #199
- [x] Closes #202
- [x] Closes #203
- [x] Closes #204
- [x] Closes #205
- [x] Closes #206
- [x] Closes #207
- [x] Closes #210
- [x] Closes #213
- [x] Closes #215
- [x] Closes #222
- [x] Closes #223
- [x] Closes #224
- [x] Closes #275
- [x] Closes #232
- [x] Closes #233
* Contributes to #335
- [x] Closes #239
- [x] Closes #241
- [x] Closes #254
- [x] Closes #255
- [x] Closes #264
- [x] Closes #265
- [x] Closes #266
- [x] Closes #271
- [x] Closes #272
- [x] Closes #273
- [x] Closes #276
- [x] Closes #278
- [x] Closes #279
- [x] Closes #284
- [x] Closes #299
- [x] Closes #317
- [x] Closes #320
- [x] Closes #326
- [x] Closes #332
* Contributes to #338
- [x] Closes #357
- [x] Closes #371
- [x] Closes #365
* Concludes [Pre-Version 2.1 Chores](https://github.com/reactive-firewall/multicast/milestone/13)
* Includes and Supersedes #280
* Includes and Supersedes #285
* Supersedes #286
* Includes and Supersedes #287
* Includes and Supersedes #290
* Includes and Supersedes #291
* Includes and Supersedes #293
* Includes and Supersedes #296
* Includes and Supersedes #305
* Includes and Supersedes #309
* Includes and Supersedes #312
* Includes and Supersedes #318
* Includes and Supersedes #321
* Includes and Supersedes #322
* Includes and Supersedes #323
* Includes and Supersedes #325
* Includes and Supersedes #327
* Includes and Supersedes #328
* Includes and Supersedes #329
* Includes and Supersedes #330
* Includes and Supersedes #334
* Includes and Supersedes #339
* Includes and Supersedes #340
* Includes and Supersedes #341
* Includes and Supersedes #342
* Includes and Supersedes #343
* Includes and Supersedes #344
* Includes and Supersedes #345
* Includes and Supersedes #346
* Includes and Supersedes #347
* Includes and Supersedes #348
* Includes and Supersedes #349
* Includes and Supersedes #351
* Includes and Supersedes #354
* Includes and Supersedes #359
* Includes and Supersedes #361
* Includes and Supersedes #373
* Includes and Supersedes #379
* Includes and Supersedes #384
* Includes and Supersedes #385
* Includes and Supersedes #388
* Includes and Supersedes #389
* Closes #390
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Patch Notes
Changes in file
docs/utils.py:impacted GHI
Summary by CodeRabbit