ci: [SDK-4493] use GH_PUSH_TOKEN for project workflow#1660
Conversation
There was a problem hiding this comment.
LGTM, straightforward CI secret rename.
Extended reasoning...
Overview
This PR makes a single one-line change to .github/workflows/project.yml, swapping the GitHub token secret used by the actions/add-to-project@v1.0.2 step from GH_PROJECTS_TOKEN to GH_PUSH_TOKEN. No SDK source code, public API, or runtime behavior is affected.
Security risks
None of concern. Both values are organization-level secrets retrieved via secrets.*, so neither is exposed in the diff. The change aligns the iOS repo with the org-wide secret used by other SDK repos for the same workflow.
Level of scrutiny
Very low. This is a CI-only configuration tweak with no logic, no source code, and no runtime impact. The action version and project URL are unchanged.
Other factors
The author noted the change will be verified post-merge by opening a test issue and confirming it lands on project 18. No bugs were flagged by the bug hunting system, and there are no outstanding reviewer comments.
Description
One Line Summary
Switch the project automation workflow to authenticate with
GH_PUSH_TOKENinstead ofGH_PROJECTS_TOKEN.Details
Motivation
The
GH_PROJECTS_TOKENsecret is being retired in favor of theGH_PUSH_TOKENorg secret used across the SDK repos for adding issues/PRs to the SDK Mobile Project board (project 18). This keeps the iOS SDK aligned with the other SDK repos.Scope
Only affects
.github/workflows/project.yml. No SDK source code, public API, or runtime behavior is changed.Testing
Manual testing
Will be verified post-merge by opening an issue and confirming the workflow run successfully adds it to the SDK Mobile Project board.
Affected code checklist
Checklist
Overview
Testing
Final pass
Made with Cursor