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 1 commit into from Jan 12, 2021


Copy link

@TheKevJames TheKevJames commented Jan 12, 2021

No description provided.

@TheKevJames TheKevJames force-pushed the config-precedence branch 2 times, most recently from 26e28a9 to 29dce07 Jan 12, 2021
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 TheKevJames force-pushed the config-precedence branch from 29dce07 to 66caaa7 Jan 12, 2021
@TheKevJames TheKevJames merged commit f4faa92 into master Jan 12, 2021
26 checks passed
@delete-merged-branch delete-merged-branch bot deleted the config-precedence branch Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant