Closes #865 - Add get_changed_items() utility for git-based selective deployment#891
Open
vipulb91 wants to merge 2 commits intomicrosoft:mainfrom
Open
Closes #865 - Add get_changed_items() utility for git-based selective deployment#891vipulb91 wants to merge 2 commits intomicrosoft:mainfrom
vipulb91 wants to merge 2 commits intomicrosoft:mainfrom
Conversation
…selective deployment
Author
|
@microsoft-github-policy-service agree |
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Briefly describe what this PR does and why.
Adds a new public utility function
get_changed_items()to support git-based selective deployment of Fabric items.Linked Issue (REQUIRED)
#865
Motivation
Closes #865. Users running CI/CD pipelines with
fetchDepth: 2(or similar shallow clones) want to deploy only the items that changed in a given commit/ref, rather than publishing all items every time.## Approach (Option 2 — Decoupled) - Discussed in comment section with @shirasassoon
Rather than adding
changed_only/git_compare_refparameters directly topublish_all_items()andunpublish_all_orphan_items()(Option 1), this PR exposes the git-diff logic as a standalone utility function. This keeps the core publishing functions clean and allows users to compose the deployment logic themselves.New API