Skip to content
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

Update bridge-to-kubernetes-vs.md #10137

Closed
wants to merge 1 commit into from

Conversation

ProfessorMc
Copy link

Azure/Bridge-To-Kubernetes#621 removed the todo app an moved it to a custom fork for dependabot. Updated the link to the fork.

Azure/Bridge-To-Kubernetes#621 removed the todo app an moved it to a custom fork for dependabot.  Updated the link to the fork.
Copy link
Contributor

@ProfessorMc : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 9f3e393:

✅ Validation status: passed

File Status Preview URL Details
bridge/articles/bridge-to-kubernetes-vs.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

@ProfessorMc : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ShannonLeavitt
Copy link
Contributor

@ghogen

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Mar 19, 2024
@ghogen
Copy link
Collaborator

ghogen commented Mar 20, 2024

@ProfessorMc @qpetraroia
I don't think we should referencing any private forks from the documentation. Can you explain the reasoning here, also I've added a Bridge product team member for review.

@ghogen ghogen closed this Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants