Skip to content

fix: Ignoring the future folder for docs generation#382

Closed
jimbobbennett wants to merge 5 commits intomainfrom
fix/ignore-future-for-docs
Closed

fix: Ignoring the future folder for docs generation#382
jimbobbennett wants to merge 5 commits intomainfrom
fix/ignore-future-for-docs

Conversation

@jimbobbennett
Copy link
Contributor

This change ignores the __future__ folder when creating docs.

@jimbobbennett jimbobbennett requested a review from a team as a code owner October 23, 2025 23:09
@jimbobbennett jimbobbennett requested a review from lan17 October 23, 2025 23:09
@jimbobbennett jimbobbennett changed the title Ignoring the future folder for docs generation fix: Ignoring the future folder for docs generation Oct 23, 2025
@codecov
Copy link

codecov bot commented Oct 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.89%. Comparing base (82435a9) to head (db1d301).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #382   +/-   ##
=======================================
  Coverage   84.89%   84.89%           
=======================================
  Files          67       67           
  Lines        5183     5183           
=======================================
  Hits         4400     4400           
  Misses        783      783           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jimbobbennett jimbobbennett enabled auto-merge (squash) October 23, 2025 23:25
auto-merge was automatically disabled October 24, 2025 15:47

Pull request was closed

@jimbobbennett jimbobbennett deleted the fix/ignore-future-for-docs branch October 24, 2025 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants