Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • cube-doctor cube-doctor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cubicwebcubicweb
  • cube-doctorcube-doctor
  • Issues
  • #40
Closed
Open
Issue created Apr 15, 2021 by Arthur Lutz@arthurOwner

[proposed upgrades] find a way to flag and remind maintainers to take care of MR

When a MR for proposed upgrades (requirements.txt or package.json) has it's tests green it should be easy for maintainers to merge it. For red dependency upgrades that fail it could result in a "we'll handle that one later, we're focusing on features" and for theses red MRs to be forgotten or become stock.

Maybe we could have a different reminder message, for example "make sure you have an issue created explaining why this MR is not managed (for now). And that this issue is visible to the team and maybe the client too".

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking