Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Properly handle run template copying when one run type is copied to another. #242

Merged
merged 3 commits into from
Sep 22, 2024
Merged

Properly handle run template copying when one run type is copied to another. #242

merged 3 commits into from
Sep 22, 2024

Commits on Sep 9, 2024

  1. Properly handle run template copying when one run type is copied to a… 

    …nother.

This fixes an issue where the default working directory of a run was changed to the one of the template, even though a template was never created on the run type from which the working copy was cloned.

Added test to cover this behaviour.
    @marchermans
    marchermans committed Sep 9, 2024
    Configuration menu
    Copy the full SHA
    4973e19 View commit details
    Browse the repository at this point in the history

  2. Fix test case on windows that checks for working directories.

    @marchermans
    marchermans committed Sep 9, 2024
    Configuration menu
    Copy the full SHA
    68fdbc6 View commit details
    Browse the repository at this point in the history

Commits on Sep 22, 2024

  1. Fix unit test

    @marchermans
    marchermans committed Sep 22, 2024
    Configuration menu
    Copy the full SHA
    d744392 View commit details
    Browse the repository at this point in the history