You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] CLI fails for GitHub URLs with slash-based branches and multi-dot spec files #1940
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Hi! I'd like to work on this bug fix for GitHub URL parsing and file extension detection. I can fix both issues: (1) update the regex to handle branch names with slashes, and (2) improve file extension detection for multi-dot filenames. Let me know if this is still available!
I'll start investigating the root cause and submit a PR soon. If anyone else is already working on this, please let me know to avoid duplicate efforts.
I've submitted a fix for this issue in PR #2203. The PR addresses both bugs described here:
GitHub URL parsing: Converted to using raw.githubusercontent.com URLs which natively resolve the branch/path ambiguity, correctly handling branches with slashes like feature/new-validation.
File extension detection: Changed from name.split('.')[1] to parts.pop() to correctly extract the last extension segment, fixing multi-dot filenames like my.asyncapi.yaml and gracefully handling files without extensions.
Hi, I've submitted a fix for both bugs in this issue: #2209
A note on Bug 1 (slash-based branch names): several existing PRs change ([^\/]+) to (.+?) (lazy match), but lazy still resolves to the shortest segment — same broken behaviour for branches like feature/my-fix. The correct fix requires trying every possible branch/path split and retrying on 404.
My PR replaces the single-URL conversion with generateGitHubApiCandidates that produces all splits ordered shortest-branch-first, then retries only on HTTP 404 (non-404 errors propagate immediately). Bug 2 is fixed with path.extname() as in other PRs.
Activity
github-actions commentedon Dec 28, 2025
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Varadraj75 commentedon Jan 3, 2026
Hey @Shurtu-gal @Souvikns @AayushSaini101 ,
is this issue has been solved or can i work on it?
ASHISH74888 commentedon Jan 15, 2026
Hii @derberg @princerajpoot20 @Shurtu-gal ,
Is the issue still open? If so, I’d like to take it up.
l8888888 commentedon Apr 21, 2026
I've submitted a PR to fix both bugs mentioned in this issue: #2128
The PR addresses:
feature/new-validation)my.asyncapi.yaml)Both issues are now resolved. Please review when you have a chance!
BossChaos commentedon Apr 22, 2026
I'd like to work on this bug fix.
Plan:
feature/new-validation)my.asyncapi.yaml)ETA: Within 24 hours
Will submit PR once complete.
test: Add test case for slash-based branch names in GitHub URLs (asyn…
BossChaos commentedon Apr 22, 2026
✅ Implementation Complete
I've submitted PR #2131 to fix this issue.
Changes:
validation.service.tsto support slash-based branch names (e.g.,feature/new-validation)Commits:
881ecda- fix: Support slash-based branches and multi-dot spec filese68e935- test: Add test case for slash-based branch namesThe PR is ready for review. Thanks! 🙏
BossChaos commentedon Apr 22, 2026
Update
PR #2131 was submitted as duplicate of #2128. Closing in favor of #2128 by @l8888888.
Thanks!
fix: support slash-based branch names in GitHub URL parsing
fix: handle multi-dot file extensions in fileExists
zanabalofficial commentedon Apr 22, 2026
Hi! I'd like to work on this bug fix for GitHub URL parsing and file extension detection. I can fix both issues: (1) update the regex to handle branch names with slashes, and (2) improve file extension detection for multi-dot filenames. Let me know if this is still available!
BossChaos commentedon Apr 22, 2026
Hi @akashcorex, thanks for reporting this issue!
I'd like to work on fixing both bugs:
I'll start investigating the root cause and submit a PR soon. If anyone else is already working on this, please let me know to avoid duplicate efforts.
你好 @akashcorex,感谢报告这个问题!
我想负责修复这两个 bug:
我会开始调查根本原因并尽快提交 PR。如果其他人已经在处理这个问题,请告诉我以避免重复工作。
3 remaining items
fix: GitHub URL parsing and file extension detection for issue asynca…
bobbiejaxn commentedon May 7, 2026
I have submitted PR #2187 to fix this issue.
Approach:
feature/new-validation). Usesraw.githubusercontent.comfor simpler, more reliable file resolution.name.split('.')[1]withpath.extname()which correctly handles multi-dot filenames (e.g.,my.asyncapi.yaml→.yaml).All CI checks pass (SonarCloud clean, automerge approved). The changes are minimal and focused — 3 files changed, no unnecessary refactoring.
Would appreciate a review from the maintainers. 🙏
chengyixu commentedon May 12, 2026
/attempt #1940
fix: handle GitHub URLs with slash-based branches and multi-dot filen…
fix: handle GitHub URLs with slash-based branches and multi-dot filen…
fix: handle GitHub URLs with slash-based branches and multi-dot filen…
wdnmdtonyma commentedon May 13, 2026
I've submitted a fix for this issue in PR #2203. The PR addresses both bugs described here:
GitHub URL parsing: Converted to using
raw.githubusercontent.comURLs which natively resolve the branch/path ambiguity, correctly handling branches with slashes likefeature/new-validation.File extension detection: Changed from
name.split('.')[1]toparts.pop()to correctly extract the last extension segment, fixing multi-dot filenames likemy.asyncapi.yamland gracefully handling files without extensions.Happy to iterate based on review feedback.
hikali123456789 commentedon May 21, 2026
I have submitted PR #2208 which fixes the multi-dot filename extension bug in fileExists(). Please add bounty label and /claim. Thank you!
tdnguyenND commentedon May 22, 2026
Hi, I've submitted a fix for both bugs in this issue: #2209
A note on Bug 1 (slash-based branch names): several existing PRs change
([^\/]+)to(.+?)(lazy match), but lazy still resolves to the shortest segment — same broken behaviour for branches likefeature/my-fix. The correct fix requires trying every possible branch/path split and retrying on 404.My PR replaces the single-URL conversion with
generateGitHubApiCandidatesthat produces all splits ordered shortest-branch-first, then retries only on HTTP 404 (non-404 errors propagate immediately). Bug 2 is fixed withpath.extname()as in other PRs.Ojas2095 commentedon May 28, 2026
I would like to work on this issue under the MICROGRANT program. I have analyzed the bug and am ready to submit a PR.
q404365631 commentedon Jun 3, 2026
I'd like to take this on! I'll fix both sub-issues:
feature/new-validation)name.split(".")Will submit a PR shortly with tests.
AayushSaini101 commentedon Jun 7, 2026
closed via: #2216 thanks