-
Notifications
You must be signed in to change notification settings - Fork 192
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
Add deleteReference #388
Add deleteReference #388
Conversation
There is no |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As commented previously
Gotcha, I'll just take I might've misunderstood the philosophy behind Is there any convention for what can or cannot be named? This code does function FWIW, even though there "is no |
@pbrisbin yes. I'd prefer change of See e.g. https://hackage.haskell.org/package/github-0.22/docs/GitHub-Data-GitData.html#t:GitCommit, there |
OK, if I'm understanding correctly: you don't want to just toss around Do you have any concerns about package API compatibility? I think changing the type of Also, total sidenote: there can exist a |
breaking changes is fine |
This is ready for re-review. |
👋 Hi there, I just wanted to check that you're not waiting on me for anything here? |
I missed that for |
Did this get missed for |
amended and merged as part of #446, thanks! Sorry for long wait. |
NOTE: I'm not sure if passing a
Name GitReference
is right, or if I should pass a fullGitReference
.For example, deleting a branch works with this code:
deleteReference auth owner repo "heads/some-branch"
. If I were required to pass a fullGitReference
, I'd have to either fake one or somehow have fetched it via a prior API call. This limitation is why I did what I did here, FWIW.