Skip to content

Discuss Server Repository Structure #6131

Description

@DominicOram

As a developer I would like to minimise the amount of time I have to spend switching branches, whilst still making sure things are tidy. We should have a discussion as to whether the current repository structure does this.

Acceptance Criteria

  • A discussion is held about how we could improve our repository structure
  • The agreed new structure is documented and a ticket created to implement

Metadata

Metadata

Assignees

Labels

3no_release_notesTickets that do not need release notes, use sparingly!

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions