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

Allow specifying custom profiles #44

Merged
merged 6 commits into from
May 13, 2023
Merged

Allow specifying custom profiles #44

merged 6 commits into from
May 13, 2023

Commits on May 9, 2023

  1. Allow specifying custom profiles 

    Allow for users to specify a specific profile.
    @afnanenayet
    afnanenayet committed May 9, 2023
    Configuration menu
    Copy the full SHA
    609508c View commit details
    Browse the repository at this point in the history

Commits on May 10, 2023

  1. Use input profile env var 

    The `release` profile was hardcoded and will fail if we change the
profile.
    @afnanenayet
    afnanenayet committed May 10, 2023
    Configuration menu
    Copy the full SHA
    8c4e615 View commit details
    Browse the repository at this point in the history

Commits on May 11, 2023

  1. Use a default value for profile 

    Set the default profile env var to "release" if it's not supplied.
    @afnanenayet
    afnanenayet committed May 11, 2023
    Configuration menu
    Copy the full SHA
    e7e9725 View commit details
    Browse the repository at this point in the history

  2. Transform profile name for special profiles 

    Address feedback about handling special Cargo profiles.
    @afnanenayet
    afnanenayet committed May 11, 2023
    Configuration menu
    Copy the full SHA
    1782ab0 View commit details
    Browse the repository at this point in the history

Commits on May 12, 2023

  1. Split profile dir and input profile 

    Use the profile name provided by the user, always. We separate out a new
variable for the profile directory name for clarity, and so we use the
correct profile as requested by the user.
    @afnanenayet
    afnanenayet committed May 12, 2023
    Configuration menu
    Copy the full SHA
    5c4b471 View commit details
    Browse the repository at this point in the history

Commits on May 13, 2023

  1. fix: Revert bad search and replace 

    We were not supposed to change the name of the field we're pulling.
    @afnanenayet
    afnanenayet committed May 13, 2023
    Configuration menu
    Copy the full SHA
    3f55a34 View commit details
    Browse the repository at this point in the history