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
When the provider is set to 'github', the current implementation fails to correctly parse URLs from GitHub Enterprise Server instances. This causes errors when users attempt to use Enterprise Server URLs with our system.
Current Behavior
URLs from github.com are parsed correctly
URLs from GitHub Enterprise Server instances throw an error or are parsed incorrectly
Expected Behavior
Both github.com and GitHub Enterprise Server URLs should be parsed correctly when the provider is set to 'github'
Update the URL parsing logic to accommodate both github.com and GitHub Enterprise Server URL structures. This may involve:
Using more flexible regex patterns
Adjusting the logic to handle varying URL formats
Ensuring that repository names and PR/issue numbers are correctly extracted regardless of the exact URL structure
Additional Notes
This issue is related to the recent changes made in the PR and issue URL parsing functions. While those changes improved the situation, they didn't fully address the Enterprise Server use case.
The text was updated successfully, but these errors were encountered:
Description
When the provider is set to 'github', the current implementation fails to correctly parse URLs from GitHub Enterprise Server instances. This causes errors when users attempt to use Enterprise Server URLs with our system.
Current Behavior
Expected Behavior
Steps to Reproduce
Proposed Solution
Update the URL parsing logic to accommodate both github.com and GitHub Enterprise Server URL structures. This may involve:
Additional Notes
This issue is related to the recent changes made in the PR and issue URL parsing functions. While those changes improved the situation, they didn't fully address the Enterprise Server use case.
The text was updated successfully, but these errors were encountered: