feat: added Best practices on how to deploy GIT connected Apps that are using packages. #2979
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
… need to be clicked, ie where edit and view mode of GIT connected App are out of sync.
subrata71
previously approved these changes
Dec 22, 2025
…ent of Apps using packages.
subrata71
approved these changes
Dec 22, 2025
tomjose92
deleted the
feat/issue-2978/best-practices-git-with-package
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Added Best practices on how to deploy GIT connected Apps that are using packages. This documentation talks about both scenarios, ie GIT connected and non GIT connected packages.
Also talks about how to use CI/CD in such cases
Provide a concise summary of the changes made in this pull request
Pull request type
Check the appropriate box:
*
Documentation tickets
2978
Link to one or more documentation tickets:
Checklist
From the below options, select the ones that are applicable: