Manifests gone?

Open
#45 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, docker, javascript, node.js
Domain
build-system, devops, documentation

Research direction

Inspect the README and the manifests folder references, then compare the current repository with its history to determine whether the missing .yml files were intentionally removed. Check the linked Microsoft learning path for the expected demo flow. Done means the README and repository contents provide a working, consistent path for the demo.

Written by the indexing model from the issue text.

Description

Looks like the manifests folder with the .yml files was removed? Why/how do we use this for the demo now? I will go back to pull the history that contains these files, but the readme calls out the existence of files that don't exist in the repo currently, as well as following the learning path on the MS website (https://learn.microsoft.com/en-us/azure/aks/devops-pipeline?pivots=pipelines-yaml#get-the-code) now doesn't really work.

Dominant language
JavaScript
Stars
73
Forks
3.1k
No merged PRs in 30d

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.

More from MicrosoftDocs/pipelines-javascript-docker

All issues in MicrosoftDocs/pipelines-javascript-docker

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.