Skip to content

docs: explain package source vs installed copies - #2599

Open
Aryan Singh K. (aryansk) wants to merge 1 commit into
microsoft:mainfrom
aryansk:docs/2183-source-vs-installed
Open

docs: explain package source vs installed copies#2599
Aryan Singh K. (aryansk) wants to merge 1 commit into
microsoft:mainfrom
aryansk:docs/2183-source-vs-installed

Conversation

@aryansk

Copy link
Copy Markdown

Closes #2183

Summary

  • add a package-authoring guide explaining canonical source files versus materialized consumer copies
  • document the recommended git dependency + ref workflow
  • clarify same-repository authoring and the current lack of a live-link development mode

Validation

  • documentation-only change; patch syntax was checked against current main

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds new documentation clarifying the distinction between an APM package’s canonical source repository and the installed (materialized) consumer copy, with recommended workflows for authors and consumers.

Changes:

  • Documented “source vs installed” package concepts and best practices (don’t edit/commit installed copies).
  • Added a step-by-step recommended author/consumer workflow with an example git: dependency.
  • Clarified guidance for authoring and consuming within the same repository, including testing recommendations.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +52 to +55
APM does not currently provide a live-link/development-install mode that keeps
an installed consumer copy synchronized with edits in the source checkout. If
you need immediate feedback while authoring, test from the source repository or
re-run the install/update workflow after changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Question : How to avoid duplicated AI primitives when those are present in Git repo and install in dev local computer

2 participants