New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate getCurrentCommittish
and GitHubURL
here?
#142
Comments
I think we can extract it to be its own module, I like how simple this one is no need to complicated it. @refined-github/maintainers thoughts? |
To be fair, I think most Footnotes
|
Well be glad to host them. That's refined-github for you 🤪 |
Things I'm not excited about:
I wouldn't be totally opposed to publishing a "gh extensions utils" package but I'd probably suggest using |
I'll add, even if we go to the trouble of doing all of that, it doesn't mean it actually helps that many people. See how many repos use this very simple, very old package: https://github.com/refined-github/github-url-detection/network/dependents Here's the total of 2 non-fork non-ghosttown extensions that use it:
I'd argue we didn't even need to extract |
Exactly why we extracted, the tests took too much time. |
@fregante Really good points. I agree it's too much hassle for those simple helpers, I brought up about this one because I think it's an exception:
|
PR welcome to add those two:
|
Another GitHub-related browser extension Gitako encountered the infamous "slash-in-branch-name" issue: EnixCoda/Gitako#243
Refined GitHub had similar experience and that (along with other issues) resulted in the
GitHubURL
helper (and its dependencygetCurrentCommittish
). I think these helpers are generally useful for others as well, so is there any interest maintaining them here?Issue with this approach is that the helpers are huge comparing to the existing
getRepo
helper. And it's not super related to URL detection, so it probably should be its own thing.The text was updated successfully, but these errors were encountered: