Skip to content

Make parts of generated package optional #383

@sjvrijn

Description

@sjvrijn

What

As mentioned during the discussion session on April 18, this template is frequently used as a starting point from which parts are removed after package generation. We should consider making these parts optional in the first place, so they can be enabled or disabled based on questions during setup.

Suggestions welcome for which parts to make optional!

How

Sections within files can be managed using the Jinja templating language, and optional files can be removed after generation by using the post_gen_project hook

Candidate Parts

  • SonarCloud
  • GitHub Actions (in case of using e.g. GitLab instead)
  • ...

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions