Skip to content

additional: cleanXXX #45

@Reissner

Description

@Reissner

You describe a subfolder toolbox describing the part of the proper toolbox,
i.e. the part to be delivered.
Outside of that you suggest e.g. a readme file, directly in the root folder.
Tests and documentation not to be delivered are further examples
for what could be in the root folder.

What I like personally very much is a file cleanXXX.m, where XXX is the name of the toolbox,
is a function or script to clean all files created in the course of development,
be it created during test or documentation.
I think this is better than using .gitignore because it ensures reproducibility.
All cleanXXX does not cleanup must be versioned and pushed.
invoking cleanXXX makes toolboxes more repoducible and avoids that rubbish or private data is deployed.

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