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

source_up_if_exists: A strict_env compatible version of source_up #921

Merged
merged 4 commits into from Apr 14, 2022
Merged

source_up_if_exists: A strict_env compatible version of source_up #921

merged 4 commits into from Apr 14, 2022

Commits on Apr 8, 2022

  1. source_up_if_exists: A strict_env compatible version of source_up 

    This fixes direnv#913

While I was in here, I opted to make the existing `source_up` script log
explicitly when it can't find a file. I think that's useful both with
strict_env enabled and disabled.
    @jfly
    jfly committed Apr 8, 2022
    Configuration menu
    Copy the full SHA
    007b0d1 View commit details
    Browse the repository at this point in the history

Commits on Apr 11, 2022

  1. Dry up the logic between source_up and source_up_if_exists 

    I'm honestly not sure if this is better or worse. See this review
feedback discussion for more information:
direnv#921 (comment)
    @jfly
    jfly committed Apr 11, 2022
    Configuration menu
    Copy the full SHA
    c16ba42 View commit details
    Browse the repository at this point in the history

  2. Update the direnv-stdlib man page with info about source_up_if_exists.

    @jfly
    jfly committed Apr 11, 2022
    Configuration menu
    Copy the full SHA
    992eea4 View commit details
    Browse the repository at this point in the history

Commits on Apr 14, 2022

  1. fixups

    @zimbatm
    zimbatm committed Apr 14, 2022
    Configuration menu
    Copy the full SHA
    c7099d6 View commit details
    Browse the repository at this point in the history