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.

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

feat(config): reorder configuration precedence #249

Merged
merged 1 commit into from Jan 12, 2021

Commits on Jan 12, 2021

  1. feat(config): reorder configuration precedence

    We've been getting a slew of cases where users are reporting requiring
    different configurations -- especially Github Actions, where we seem to
    need to set a different service name on a case-by-case basis.
    
    Reordering our configuration precedence such that user-specified values
    overwrite the CI defaults should allow users to fix these problems
    without requiring a one-size-fits-all code change.
    
    This is massively backwards incompatible for anyone with the same key
    set to two different values in their configs.
    TheKevJames committed Jan 12, 2021
    Copy the full SHA
    66caaa7 View commit details
    Browse the repository at this point in the history