Title:

How can I safely inspect a STAGED changeset without applying it?

Body:

Hello,

I’m working in a staging environment and Railway is reporting a STAGED changeset on one service.

The situation is:

• the service is connected to the GitHub main branch;
• auto deploy is currently disabled;
• the latest deployed version is still the previous commit;
• Railway reports a STAGED changeset;
• the staged state lists the same 15 variable names that already exist in the current service configuration;
• staged.config appears empty;
• variable values are redacted, so I cannot safely compare current vs staged values.

I do NOT want to apply, discard, redeploy, or reveal any secret values just to understand what is pending.

Could someone clarify:

1. Is there a safe way to inspect the effective diff between the current and STAGED configuration without revealing secret values?
2. Can Railway show which variables are actually added, changed, removed, or unchanged?
3. Can a STAGED changeset exist even if there is no effective difference in the variable values?
4. If I manually deploy only the new application code from GitHub, will the STAGED changeset remain separate, or could it be applied as part of that deployment?
5. What is the safest way to deploy only the new application code while leaving the STAGED changeset untouched?

Please do not ask for secret values. I’m only looking for read-only guidance.

Thank you.