Glitch GitHub import as restore: does it overwrite or preserve .env secrets and uploaded assets?

Goal

I want to use Glitch's documented GitHub export/import feature as a backup-and-restore path for a project's source, and I need to know exactly what state a re-import recovers before I rely on it.

Constraint and uncertainty

Export to GitHub captures the project file tree, but my understanding is that .env secrets are typically excluded from the repository, and uploaded assets live on CDN URLs tracked in metadata such as .glitch-assets rather than as binaries in the repo. That leaves the core restore semantics unclear: when I import the repository back into a project that already has modified .env values and deleted assets, does the import act as an authoritative overwrite of project state, or does it merge and preserve current secrets and asset references?

I plan to verify in a disposable project with a throwaway secret and one small test asset, since feature availability may differ by project type and the current product behavior needs confirmation.

Questions

• Does importing from GitHub replace the existing .env contents, leave them untouched, or merge keys?
• After a round-trip, are previously uploaded assets still served from their original CDN URLs, or do references break?
• Is there any documented way to make the restore fully authoritative over hosted state rather than source files only?