Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Community Edition
GitLab Community Edition
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 14,492
    • Issues 14,492
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 811
    • Merge Requests 811
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Community EditionGitLab Community Edition
  • Merge Requests
  • !7926

Merged
Opened Dec 05, 2016 by Ershad Kunnakkadan@ershadk5 of 9 tasks completed5/9 tasks
  • Report abuse
Report abuse

Feature to create directly addressed Todos when mentioned in beginning

What does this MR do?

Adds a feature to create a 'directly addressed' Todo when @user (or multiple users) are mentioned in the beginning of a note.

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

Why was this MR needed?

Screenshots (if relevant)

Screen_Shot_2016-12-06_at_3.18.56_am

Does this MR meet the acceptance criteria?

  • Changelog entry added
  • Documentation created/updated
  • API support added
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Branch has no merge conflicts with master (if it does - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

Closes #24976 (closed)

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch https://gitlab.com/ershadk/gitlab-ce.git 24976-start-of-line-mention
git checkout -b ershadk/gitlab-ce-24976-start-of-line-mention FETCH_HEAD

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout origin/master
git merge --no-ff ershadk/gitlab-ce-24976-start-of-line-mention

Step 4. Push the result of the merge to GitLab

git push origin master

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 65
  • Commits 1
  • Pipelines 36
  • Changes 14
Ershad Kunnakkadan
Assignee
Ershad Kunnakkadan @ershadk
Assign to
9.0
Milestone
9.0
Assign milestone
Time tracking
3
Labels
Community contribution Platform [DEPRECATED] todos
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ce!7926

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.