-
-
Notifications
You must be signed in to change notification settings - Fork 395
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
Subscribe to/Unsubscribe from an Issue or Merge Request #221
Labels
help wanted
Good for newcomers
Comments
Unsubscribe should be implemented as |
newellista
pushed a commit
to newellista/gitlab
that referenced
this issue
Feb 23, 2017
This resolves NARKOZ#221 Note that the documentation in the issue is incorrect wrt to the unsubscribe endpoints. Latest Gitlab documentation indicates that a `POST` to `.../unsubscribe` is the correct method, rather than `DELETE`. Also, verbs are `subscribe`/`unsubscribe` rather than `subscription`
asedge
pushed a commit
that referenced
this issue
Mar 3, 2017
epintozzi
pushed a commit
to epintozzi/gitlab
that referenced
this issue
Mar 8, 2017
* Update merge_request endpoints to new merge_requests endpoints. Resolves NARKOZ#229. * (Un)subscribe to issues and merge_requests. Resolves NARKOZ#221.
epintozzi
pushed a commit
to epintozzi/gitlab
that referenced
this issue
Mar 13, 2017
* Update merge_request endpoints to new merge_requests endpoints. Resolves NARKOZ#229. * (Un)subscribe to issues and merge_requests. Resolves NARKOZ#221.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add
subscribe_to_*
andunsubscribe_from_*
methods tolib/client/issues.rb
andlib/client/merge_requests.rb
.subscribe_to_issue
/subscribe_to_merge_request
:POST /projects/:id/issues/:issue_id/subscription
POST projects/:id/merge_requests/:merge_request_id/subscription
unsubscribe_from_issue
/unsubscribe_from_merge_request
:DELETE /projects/:id/issues/:issue_id/subscription
DELETE /projects/:id/merge_requests/:merge_request_id/subscription
The text was updated successfully, but these errors were encountered: