Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33847

Closed (moved)
Open
Opened Apr 08, 2020 by anarcat@anarcat💬

teach zwiebelbot about GitLab

Part of the gitlab migration will require a change to the IRC bot telling us about issue titles (and statuses).

Right now, when we say "#N" (e.g. #1234 (closed)) in a tor channel, it fetches the bug #N title/status from Trac and displays it in the IRC channel, like so:

14:12:53 <+anarcat> #23933
14:12:54 -zwiebelbot:#tor-project- tor#23933: Add a configuration framework - [closed] - https://bugs.torproject.org/23933

We would need to do something similar so that the bot could also talk to Trac.

Since GitLab issues are project-specific (ie. you can have two different issue 1 in two different projects), we would need a prefix to make this work. So it would look something like:

<anarcat> tpo/web/community#105
<zwiebelbot> Update link to Support portal (#105) - https://gitlab.torproject.org/torproject/web/community/-/issues/105

ie. it should match a PATH#NUMBER pattern which gets turned into https://gitlab.torproject.org/PATH/-/issues/NUMBER.

Eventually, we would also retire the #N redirection we currently have pointed at Trac and have those pointing at the legacy project in GitLab instead. but that can be done later.

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