Replies: 1 comment
-
The ask is to identify, after the creation or refresh of a sandbox or scratch org, which source-format files are expected to be different from the source org's source-format files? At a higher-level, I am trying to identify which changes are and are not candidates for migration back to the source org. Yes, it is possible to tell git diff to ignore some files when I'm doing a diff between two orgs' source-format files. For example, we could tell git diff to ignore/exclude all of the files that haven't changed since the org was created/refreshed. So..... maybe I have answered my own question. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Org/Environment-specific metadata/files: Is there a definitive list?
(Examples of such files in source format include
connectedApps/DevOps_Center.connectedApp-meta.xml
andsettings\MyDomain.settings-meta.xml
.)BTW: Do you have a brand new production instance? If so, you can help us start this list :)
Keywords for future searchers: "org specific metadata" "org specific data" "org specific files" "org specific source" "environment specific metadata" "environment specific data" "environment specific files" "environment specific source"
Beta Was this translation helpful? Give feedback.
All reactions