Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 330
    • Issues 330
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40023
Closed
Open
Issue created Jul 02, 2020 by Alexander Færøy@ahf🍍Owner0 of 2 checklist items completed0/2 checklist items

Use Gitlab CI with Bots for Code Quality and Technical Debt checks

Once we have Gitlab CI on this Gitlab instance, we should look into which checks we want to have for Tor itself. This could be done either directly in the CI via different soft-fail options, but it could also be implemented as a bot.

Tasks

  • Check for function complexity changes (like with Practracker).
  • Check for coverage changes from tests (like we have on Github).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking