Summary

If the Personal Access Token (PAT) used for an external Git repository (e.g., GitHub) expires, merge operations in Sztab fail during the push step.

There is currently no way to update the stored PAT via the Project Edit UI. The only workaround is to either:

• Create PATs with long expiration periods, or
• Manually update the PAT directly in the database.

This is a functional gap and creates operational risk.

Environment

Version: 1.9.2
Component: Sztab + Sztabina
External Git: GitHub (PAT-based authentication)

Steps to Reproduce

1. Configure a Project with an external Git URL (e.g., GitHub).
2. Provide a valid PAT.
3. Allow the PAT to expire.
4. Attempt a merge (regular, squash, rebase, or ff).
5. Observe that merge completes locally but push fails.
6. Navigate to Project → Edit.

Actual Behavior

• Merge operation in Sztabina succeeds locally.
• Push to remote fails due to expired PAT.
• Sztab reports merge failure.
• Project Edit screen does not allow updating the stored PAT.
• No recovery path is available via UI.

Expected Behavior

• Project Edit screen should allow updating Git credentials (username + PAT).
• System should clearly report authentication failure.
• Merge operation should not leave repository in inconsistent state.

Impact

• Users are blocked from completing merges.
• No self-service recovery path.
• Requires direct DB intervention.
• Operationally fragile for short-lived tokens.

Current Workaround

1. Generate PATs with long expiration times.
2. Or manually update the PAT in the database.
3. Restart stack if necessary.

Suggested Fix

1. Extend Project Edit UI to allow updating Git credentials.
2. Validate credentials on save (optional).
3. Improve error messaging on push failure.
4. Consider detecting 401/403 from remote and surface as "Authentication expired".

Severity

Medium–High

Blocks merge workflow once token expires.