Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • CMake CMake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Eli F-F
  • CMakeCMake
  • Repository

Switch branch/tag
  • cmake
  • Help
  • dev
  • review.rst
Find file BlameHistoryPermalink
  • Craig Scott's avatar
    Help: Document the expire and external discussion resolve states · 49f5b6f7
    Craig Scott authored May 26, 2019
    Our practice of closing MRs temporarily while discussion
    takes place in a separate issue isn't always well understood
    by MR authors. Expiring a MR seems to be better understood,
    but making it clear that it is also a temporary state is helpful.
    49f5b6f7

Replace review.rst

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.