Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Packages
    • Packages
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD Analytics
    • Code Review
    • Insights
    • Issues Analytics
    • Repository Analytics
    • Value Stream Analytics
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge Requests
  • !14016

Merged
Opened Sep 03, 2017 by Hiroyuki Sato@hiroponz🇯🇵4 of 11 tasks completed4/11 tasks
  • Report abuse
Report abuse

Add my_reaction_emoji param to /issues and /merge_requests API

  • Overview 10
  • Commits 3
  • Pipelines 7
  • Changes 9

What does this MR do?

Follow-up from "Add filter by my reaction" (!12962 (merged))

Are there points in the code the reviewer needs to double check?

No.

Why was this MR needed?

It is need to be consistent with the issues/merge requests filter feature.

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests added for this feature/bug
  • Review
    • Has been reviewed by UX
    • Has been reviewed by Frontend
    • Has been reviewed by Backend
    • Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together

What are the relevant issue numbers?

Nothing.

Edited Sep 04, 2017 by Hiroyuki Sato
Assignee
Assign to
10.0
Milestone
10.0
Assign milestone
Time tracking
3
Labels
Community contribution api award emoji
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-foss!14016

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.