-
-
Notifications
You must be signed in to change notification settings - Fork 7
Add method to deploy content files #361
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
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
I'm still going to work on this, just need it to bump up in my list of todo's :) |
Perfect. I just wanted to check where the build failed! |
Description
Motivation and Context
The Visual Studio extension deploys all files that are marked as
Content
withAlways
orCopy if Newer
, but the vscode addon doesn't provide a similar mechanism. This PR adds a method to the vscode addon to deploy content files in a similar way.How Has This Been Tested?
NB: Not tested yet, I'm struggling with getting the extension to work locally. I suspect node version mismatches.
Screenshots
Types of changes
Checklist: