Add todo-to-issue GitHub Action in order to add GitHub Issues from TODOs, etc.

[Stelzi79]

I have found a GitHub Action (alstr/todo-to-issue-action ) that finds TODOs, FIXMEs, etc in coding files and creates GitHub Issues.

What todo-to-issue-action does:

This action will convert newly committed TODO comments to GitHub issues on push.

Optionally, issues can also be closed when the TODOs are removed in a future commit.

Action supports:

• Multiple, customizable comments identifiers (FIXME, etc.),
• Configurable auto-labeling,
• Assignees,
• Milestones,
• Projects (classic).
• todo-to-issue works with almost any programming language.

This action needs the Workflow permissions setting Read and Write permissions under Settings => Actions => General set in order to be allowed to create issues!

Before (or shortly after the merge) the action needs to be updated to point to the main branch (or whatever condition) in order to look at the main branch for TODOs on pushes.

When the TODO, etc. is removed the Issue is closed automatically. This can be configured. The automatic labeling (Fix me, Help Wanted, etc.) of issues also can be configured.

As an example on how to use it, I added a TODO in src/TagzApp.Common/Models/Content.cs. In my testing in my forked repo this worked. This is the Issue it created for #2!

I also added an .editorconfig that sets spaces as intentation for .yml files in the root directory.

Next Step:

• add all TODOs, FIXMEs, etc. in changes to the repo

[csharpfritz]

Very cool update, and will help make it clear how our team collaborates and marks up code