Feature-Request for Blueprints

[stbischof]

• [x] Templates I would like to use templates in the content: | section of a file. Templates could be projekt.url or `projekt.name' or all in the configuration accessible data of a project.

• [ ] Pattern I would like to use a regex in the content. This way i could restrict general parts of a file but open it for project specific parts using the regex pattern

• [ ] PullRequest When setting up a new Project a PR would be welcome that is generated from the Blueprint descriptions

• [ ] Create Issues on Project Would be nice if a Issue could be created on the Project that does not match the Blueprint description. ( With link to Description file)

[netomi]

• templates are clear and should be really supported
• can you have an example for a regex? what should actually happen?
• not sure about the PullRequest either, what should the PR change?
• so creating an issue instead of a PR to remediate? could be an option indeed

[stbischof]

Regex pattern:

Expecting you have a . editorconfig file in each repo. That describes the general formatting and should be same over all repos. But some repos need additional settings that are spectial to this repo and are not relevant to other repos. You will need a Blueprint that defines the first lines and then allowes optional things using regex.

PR/issue:

Odeerdog should observer the diff between Templates an repos.

When there is a diff, it should, depending on a config flag;

• create a pr with a fix
• create an issue an reminder

This way a person who do not know about otterdog knows what to do.

The Blumenprint config might have fields for the issue/pr title and body.

[netomi]

alright that makes it clear, these requests make sense.

btw. I have opted in the sub issue beta, so when we get enrolled I can create sub issues out of these tasks