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

bundle_replacements should only be a dictionary #445

Conversation

arewm
Copy link
Contributor

@arewm arewm commented Oct 25, 2022

If it is not configured, it should be set as an empty dictionary instead of None.

Signed-off-by: arewm arewm@users.noreply.github.com

@arewm arewm force-pushed the non-None-bundle-replacement branch 6 times, most recently from 420bb5b to 7411de5 Compare October 25, 2022 19:40
If it is not configured, it should be set as an empty dictionary instead
of None.

Signed-off-by: arewm <arewm@users.noreply.github.com>
@arewm arewm force-pushed the non-None-bundle-replacement branch from 7411de5 to f147080 Compare October 25, 2022 19:40
@arewm
Copy link
Contributor Author

arewm commented Oct 25, 2022

Follow on from #429 -- @yashvardhannanavati, can you review this please? I didn't catch the mismatch between {} and None defaults while I did the work in two steps.

@yashvardhannanavati yashvardhannanavati merged commit 9691e1a into release-engineering:master Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants