chore: add release config for FeatureManagement provider #135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
toddbaert
commented
Jan 15, 2024
beeme1mr
approved these changes
Jan 22, 2024
austindrenski
approved these changes
Jan 22, 2024
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
toddbaert
force-pushed
the
chore/add-FeatureManagement-release-config
branch
from
cb30ae8
to
9ed5c7a
Compare
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a couple things related to #129, specifically it adds release config and component owners info to the new FeatureManagement provider so that it will be packaged and published to nuget.
Note that before we can actually release this, we need a README with some basic usage, including whatever runtime versions/deps are required for the new variants features to work.
@ericpattison I've made you a "component owner" which will add you to PRs for this component, including releases. Note that for this automation to work, you will need to accept your org invite after signalling an approval on this PR.