Skip to content

Rename document set #353

@jstray

Description

@jstray

For a variety of reasons:

  • so users can tell themselves what they're doing
  • when importing the same docset multiple times (say, different versions) it becomes difficult to know what document set is what version.
  • important to have good names on example docsets

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions