Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 239
    • Issues 239
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #786
Closed
Open
Created Jun 14, 2022 by Marcin Siodelski@marcinMaintainer0 of 2 tasks completed0/2 tasks

Consider moving Stork developer guide to its own document

In ticket #709 (closed) we are adding a lot of new text pertaining to running and developing system tests. I think it may now deserve its own document because a lot of it is not interesting to a regular user.

  • review available tools (that can parse JS, go, ... code)
  • migrate Developer's Guide section to this new format
Edited Jun 21, 2022 by Tomek Mrugalski
Assignee
Assign to
Time tracking