Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vidjil
vidjil
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,688
    • Issues 1,688
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 84
    • Merge Requests 84
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • vidjil
  • vidjilvidjil
  • Issues
  • #4080

Closed
Open
Opened Dec 03, 2019 by Mathieu Giraud@magiraudOwner

CloneDB sur clones ayant déjà des warnings

Quand un clone a déjà un client-warning , on n'a pas de retour visuel quand on a un match de app-clonedb dessus. Par exemple, depuis !550 (merged) :

https://vdd.vidjil.org/browser/?set=26912&config=25&clone=8 avec le plus gros clone en IGKV2D-30 du 2è sample

#3135 et priorité des warnings ? #4049 ? Ou séparer emplacement warnings et CloneDB (bof) ?

Au passage, on n'a jamais de retour visuel quand on n'a pas de match de app-clonedb...

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: vidjil/vidjil#4080