Update customized QBCore resources safely

Never overwrite a customized resource with a fresh download. Use Git to make the source and target states explicit.

Inventory

For each resource record its upstream URL, deployed commit, local branch, uncommitted files, database migrations, config ownership, and dependent resources.

git remote -v
git status --short
git rev-parse HEAD
git log --oneline --decorate -10

Compare without changing production

git fetch origin main
git diff --stat HEAD..origin/main
git diff HEAD..origin/main -- fxmanifest.lua config.lua

Review code and SQL in staging. Do not run repository-wide commands with an unresolved resource variable and do not assume every QBCore repository uses identical branches or file layouts.

Rollout

1. Back up files and database; restore them on staging.
2. Create an update branch from the deployed commit.
3. Merge or cherry-pick reviewed upstream changes.
4. Resolve local config/code changes deliberately.
5. Run focused and end-to-end smoke tests.
6. Deploy during a maintenance window with predefined rollback triggers.
7. Tag or record the verified deployment commit.

Use the compatibility checklist and backup guide. When two customized resources fight over the same files, resolve it with the resource update conflicts guide.