Skip to content

Conversation

@azchohfi
Copy link
Contributor

No description provided.

@azchohfi azchohfi force-pushed the alzollin/build_changes branch from 973b04b to 1dc4770 Compare February 27, 2025 01:50
@michael-hawker
Copy link
Member

@Arlodotexe any concerns if we just merge this and test it out with other changes that happen to see how it works in practice?

@Arlodotexe
Copy link
Member

@Arlodotexe any concerns if we just merge this and test it out with other changes that happen to see how it works in practice?

It appears to be running without issue in the CI here, but since it's fully untested I'm wary of merging into main.

There're two roads to take here:

  • Move the code into a script file that can be reused and tested
  • Merge this and watch it like a hawk in case it breaks

Arlodotexe added a commit to CommunityToolkit/Tooling-Windows-Submodule that referenced this pull request Apr 6, 2025
@michael-hawker
Copy link
Member

@Arlodotexe I approved your new tooling 281 the other week, can that be merged so we can get this updated and merged in to move forward on it? Thanks!

@Arlodotexe Arlodotexe moved this to 👀 In review in Toolkit 8.x Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants