Consider Decoupling the Submit-AzureSdkForNetPr Task into Smaller SubTasks

[jorgerangel-msft]

In https://github.com/microsoft/typespec/blob/main/packages/http-client-csharp/eng/pipeline/publish.yml, we run the login-to-github.yml template job to authenticate before we run the Submit-AzureSdkForNetPr.ps1 script. The authenticated token is only valid for a few minutes, and the regen job usually takes at most an hour. Rather than having to request a new token inside of the script itself before we call git push we should consider splitting the script up into multiple smaller tasks:

1. Regenerate libraries
2. Commit changes
3. Call auth script to fetch token
4. Call git push

[github-actions]

🎯 Issue Triage

This is a feature request to improve the Submit-AzureSdkForNetPr.ps1 pipeline script by splitting it into smaller subtasks so that authentication token renewal happens just before git push, avoiding token expiry during the (potentially hour-long) regen job.

Category: Feature Request

Area: emitter:client:csharp

🔍 Analysis

• Affected file: packages/http-client-csharp/eng/pipeline/publish.yml
• The current flow fetches a GitHub auth token at the start of the pipeline job, but the token expires after a few minutes while the regeneration step can take up to an hour.
• Proposed refactor splits the monolithic script into four sequential subtasks: (1) regenerate, (2) commit, (3) re-authenticate, (4) push — so the token is fresh when needed.
• No duplicates found.

📝 Suggested next steps

• Split Submit-AzureSdkForNetPr.ps1 into the four subtasks described in the issue.
• Update publish.yml to call the auth template immediately before the git push step.
• Verify the pipeline still works end-to-end after the refactor.

Generated by Agentic Triage