Fallout-build / Fallout-build/Fallout
Auto Migrate on Nuget restore (or similar)
- Dominant language
- C#
- Stars
- 154
- Forks
- 19
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 15
Description
### Description
As per @IT-VBFK 's suggestion, what about running the migration automatically via a flag?
`` could trigger
a) upgrading the Fallout packages to a newer version
b) run the migrate cli to tackle the migration
This could also be something that goes into an IDE extension similar to the dotnet upgrade tool back in the `dotnet framework` to `dotnet core` days
### Usage Example
_No response_
### Alternative
_No response_
### Could you help with a pull-request?
No
Contributor guide
Research direction
Start by reviewing the NuGet restore flow and the existing migrate CLI entry point; the issue does not name files or tests. Define the scope first, including whether automatic package upgrades, CLI execution, or an IDE extension is intended, then establish tests for the selected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100