ci: [SDK-4485] use GH_PUSH_TOKEN for project workflow

[fadi-george]

Description

One Line Summary

Switch the project automation workflow to authenticate with GH_PUSH_TOKEN instead of GH_PROJECTS_TOKEN.

Details

Motivation

The GH_PROJECTS_TOKEN secret is no longer the standard token used for adding issues/PRs to the SDK Cross-Platform Project board. Aligning on GH_PUSH_TOKEN matches what the other SDK repos use and keeps the project automation working.

Scope

Only affects .github/workflows/project.yml. No SDK source code, public API, or runtime behavior is changed.

Testing

Manual testing

Will be verified by observing the workflow run successfully add a new PR/issue to the SDK Cross-Platform Project board after merge.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed (CI-only change)
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible (workflow change, validated post-merge)

Final pass

• Code is as readable as possible.
• I have reviewed this PR myself, ensuring it meets each checklist item

Made with Cursor

[claude]

LGTM — single-line CI token swap to align with the standard secret used across SDK repos.

Extended reasoning...

Overview

This PR makes a single one-line change in .github/workflows/project.yml, swapping the token reference from secrets.GH_PROJECTS_TOKEN to secrets.GH_PUSH_TOKEN for the actions/add-to-project@v1.0.2 step that adds new issues to the SDK Cross-Platform Project board.

Security risks

None of concern. Both values are GitHub Actions secrets resolved at runtime; no secret material is exposed in the diff. The workflow trigger (issues: opened) and target project URL are unchanged, so the blast radius is limited to project-board automation.

Level of scrutiny

Very low. This is a CI-only configuration change with no impact on SDK source, public API, or runtime behavior. Correctness will be observable post-merge by whether the next opened issue lands on the project board.

Other factors

No prior reviews or comments on the PR. The change matches the stated motivation (aligning with other SDK repos on GH_PUSH_TOKEN) and the bug hunting system found no issues.