Skip to content

Consider adding templates that discourages creating issues or PRs about contents or tooling here #52

Open
@divega

Description

@divega
  • Issues about content should go in the EF Core or EF6 repos
  • Issues about incorrectly generated docs from correct documentation need to go in whatever repo is used to develop the tools (not shure which one).

Otherwise can we can just disable issue tracking here and add the latter in the readme (the link to the product repos for content are already there).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions