Feature/GitHub connector enhancements#43
Merged
Conversation
Off by default to preserve the fixed-depth <prefix>/<dir>/<file><ext> behavior; enable to scan every folder under the prefix (or the whole repo if blank) and match by extension at any depth. In recursive mode, the full repo-relative path is used as the semantic identifier so same-named files in different folders stay distinguishable. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PyGithub asserts `path` is NotSet or a str, so passing `None` (what `self.path_prefix or None` resolves to in recursive mode with a blank prefix) raises AssertionError during the polling commit-window check. Drop the kwarg entirely when there's no prefix, matching the since/until conditional-kwarg pattern. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
[Provide a brief description of the changes in this PR]
How Has This Been Tested?
[Describe the tests you ran to verify your changes]
Backporting (check the box to trigger backport action)
Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.