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

packages.config resolver #114

Merged
merged 8 commits into from
Sep 28, 2023
Merged

packages.config resolver #114

merged 8 commits into from
Sep 28, 2023

Conversation

emilwareus
Copy link
Contributor

No description provided.

@emilwareus emilwareus changed the title initial support for packages.config resolution packages.config resolver Sep 8, 2023
@ProgHaj ProgHaj force-pushed the nuget-resolver branch 2 times, most recently from 726ae57 to ee6612b Compare September 18, 2023 14:32
Base automatically changed from nuget-resolver to main September 19, 2023 10:30
@emilwareus emilwareus force-pushed the packages-config-resolution branch from 1ddccfb to 97aff59 Compare September 26, 2023 07:37
@emilwareus emilwareus force-pushed the packages-config-resolution branch from 43d1fba to e9b14a7 Compare September 26, 2023 12:59
@github-actions
Copy link

CodeScene PR Check


View detailed results in CodeScene

Quality Gates ✅ OK
Recommended Review Level Lightweight sanity check
Declining Code Health 1 findings(s) 🚩
Improving Code Health 0 findings(s) ✅
Affected Hotspots 0 files(s) 🔥

🚩 Negative Code Health Impact (highest to lowest):

  • Large Method cmd_factory_test.go: TestParsePackagesConfig

@sweoggy sweoggy merged commit 9554a96 into main Sep 28, 2023
9 checks passed
@sweoggy sweoggy deleted the packages-config-resolution branch September 28, 2023 09:05
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