Issue when creating Release through API #96
Comments
|
I believe this is something that was not added to the library. |
|
@Casz I only started using this library yesterday, and I haven't started digging into the code yet. Having the ability to set the |
|
https://github.com/nmklotas/GitLabApiClient/blob/master/src/GitLabApiClient/Models/Releases/Requests/CreateReleaseRequest.cs seems to only consider one use case so it will properly need to be modified |
gep13
added a commit
to gep13/GitLabApiClient
that referenced
this issue
Dec 11, 2019
As documented here: https://docs.gitlab.com/ee/api/releases/#create-a-release When creating a GitLab release, there is additional property called `Ref` which is used when the Tag that the Release is targeting doesn't exist yet. This Ref can be a SHA for a commit, another tag, or a branch name. In the testing that I have done, the tag_name property is still required, so I don't think we need to create any additional constructors, only have the ability to set the `Ref` property when required.
This was referenced Dec 11, 2019
gep13
added a commit
to gep13/GitLabApiClient
that referenced
this issue
Dec 12, 2019
As documented here: https://docs.gitlab.com/ee/api/releases/#create-a-release When creating a GitLab release, there is additional property called `Ref` which is used when the Tag that the Release is targeting doesn't exist yet. This Ref can be a SHA for a commit, another tag, or a branch name. In the testing that I have done, the tag_name property is still required, so I don't think we need to create any additional constructors, only have the ability to set the `Ref` property when required.
jetersen
pushed a commit
that referenced
this issue
Dec 14, 2019
As documented here: https://docs.gitlab.com/ee/api/releases/#create-a-release When creating a GitLab release, there is additional property called `Ref` which is used when the Tag that the Release is targeting doesn't exist yet. This Ref can be a SHA for a commit, another tag, or a branch name. In the testing that I have done, the tag_name property is still required, so I don't think we need to create any additional constructors, only have the ability to set the `Ref` property when required.
MindaugasLaganeckas
pushed a commit
to MindaugasLaganeckas/GitLabApiClient
that referenced
this issue
Mar 9, 2021
As documented here: https://docs.gitlab.com/ee/api/releases/#create-a-release When creating a GitLab release, there is additional property called `Ref` which is used when the Tag that the Release is targeting doesn't exist yet. This Ref can be a SHA for a commit, another tag, or a branch name. In the testing that I have done, the tag_name property is still required, so I don't think we need to create any additional constructors, only have the ability to set the `Ref` property when required.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have just attempted to create a GitLab Release through the API when the tag doesn't currently exist on the Repository. When I did this, I got the following response in Fiddler:
Looking at the documentation, it suggests that when the tag doesn't exist, I can specify a
Refto point to:https://docs.gitlab.com/ee/api/releases/#create-a-release
However, I don't see anywhere in the
CreateReleaseRequestclass that maps to theRefparameter.Does this exist somewhere? Or is this something that needs to be added to the GitLabApiClient?
The text was updated successfully, but these errors were encountered: