Skip to content

Publish the vertical artifacts in the dotnet "repo project" #47295

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

Closed
wants to merge 2 commits into from

Conversation

jkoritzinsky
Copy link
Member

Make the "dotnet" repo project actually do a build instead of being some root utility project. This build, however, only publishes the assets.

Unlike the approach I take in #47076, this approach allows our final "vertical" publish to use a the live Arcade logic instead of the bootstrapping Arcade.

Contributes to dotnet/arcade#15317

Depends on flow of dotnet/arcade#15572

…ome root utility project. This build, however, only publishes the assets.

Unlike the approach I take in dotnet#47076, this approach allows our final "vertical" publish to use a the live Arcade logic instead of the bootstrapping Arcade.
@ghost ghost added the untriaged Request triage from a team member label Mar 5, 2025
@jkoritzinsky
Copy link
Member Author

Closing in favor of #47076 based on offline preference for that design.

@jkoritzinsky jkoritzinsky deleted the dotnet-repo-proj branch March 18, 2025 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-VMR untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant