You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the workflow will be generic (actually organisation-shared), it will transparently keep working if we merge the repositories.
I believe dotnet pack, which is what we are using in the GitHub actions, will automatically figure out the dependencies within the packages, and export those as NuGet dependencies.
Ensure there are no more open PRs open on the other libraries.
Execution
Using this repository as base, merge in the remaining repositories as if they were separate remotes.
Since we cannot migrate issues and PR history, it makes sense to me to use the library with the most history.
Push this raw merged result directly to the main branch of this library.
Create a PR that merged the sln files, and updates the cross dependencies between libraries.
Rename beardgame/utilities to beardgame/beardkit to reflect it is now a bigger set of libraries.
Follow-up
Move all the open issues from the other libraries into this repository.
Move all the old repositories in an archived, readonly state, to maintain the closed issue and PR history.
Discuss further splitting Bearded.Utilities in smaller NuGet packages.
🆙 Improvement proposal
Combine other Bearded. libraries into the same repository.
Context
Simplifies managing dependencies (both external dependencies and internal ones), and consolidates discussions and issues in one place.
NB: this does not propose shared NuGet packages.
The text was updated successfully, but these errors were encountered: