Regenerate project files - #532
Conversation
Please don’t. This is a very bad idea as it will cause needless conflicts whenever two PRs change the schema: even if the changes to the schema are not themselves conflicting, the schema-derived generated files are almost bound to conflict, forcing the author of one PR to go through a perfectly avoidable conflict resolution once the other PR is merged first. Better to keep the generated files as they are during a development cycle and re-generate them once and for all shortly before a release (including a beta release if needed). |
|
@matentzn can we get a new alpha release that includes the regenerated files? |
This PR regenerates the project files using the
make gen-projecttarget. I mistakenly thought this was part of the release workflow. In a follow-up PR, I will implement something to make sure that any change of the underlying schema YAML is also accompanied by a regeneration of the project filesdocs/have been added/updated if necessarymake testhas been run locallytests have been added/updated (if applicable)CHANGELOG.md has been updated.