microsoft / microsoft/foundry-dev-tools

Reporting Behaviour/Solution and Exploring Collaboration for KAITO x AKS Extension Scenarios

Open
#86 1 comment 0 reactions 2 assignees View on GitHub

@swatDong is already working on this.

Since Aug 8, 2024.

Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
42m
Merged PRs (30d)
29

Description

Intro: Reporting Behavior/Solution and Exploring Collaboration for AKS Scenarios

Hiya Maintainers,

Congratulations on the successful Day-0 release of this VS Code extension! I'm reaching out to explore a possible cross-organization collaboration where we could leverage traffic from one of the AKS extensions for a specific scenario. ❤️☕️🙏

It's great to see that Mac and other distro support will be coming soon.

I'm an internal MSFT employee, and you can find me by my first name internally, Tatsat (same display picture).

Why I'm Reaching Out & What We're Looking For

We/I propose a collaboration to bridge a screen flow idea via the AKS Extension, extending it to a scenario that supports pre-population for the KAITO workspace enablement.

I look forward to discussing this in more detail.

Observations and Early days Suggesstions:
  • I see this repo is documentation only and not the real extension code reside here, but I see a small error for the first time download and for that Solution is to use the vscode API Preview Flag screenshots below for the explanation of the behaviour.

image

Preview API

image

My machine info:

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.