Assign PR author and generalize the devin workflow

[andrew-polk]

Builds on top of #7958.

What

• Renames run-devin.yml → pr-automation.yml and changes the workflow name from run-devin to PR Automation, since it now does more than just run Devin.
• Adds a step that assigns each new/updated PR to its author, so the author shows up on the PR Review Tracker board.

Why here (not in the tracker workflow)

The PR Review Tracker workflow only carries PROJECT_TOKEN (org-Projects scope, not repo writes). This workflow already declares pull-requests: write and uses the default github.token, so assignment needs no new secret or permission.

Notes

• The assign step runs first, so a failure in the later (flaky) Playwright/browser step can't cause the assignment to be skipped.
• Fork PRs are still skipped (no writable token), same as before.

🤖 Generated with Claude Code

Devin review

---

This change is 

[greptile-apps]

Greptile Summary

This PR renames run-devin.yml → pr-automation.yml and inserts a new first step that assigns each non-fork PR to its author via gh pr edit --add-assignee, enabling the author to appear on the PR Review Tracker board.

• The assign step uses environment variables for all GitHub context values (PR number, author login, repo), avoiding shell/YAML injection risks, and relies on the existing pull-requests: write permission with the default github.token — no new secrets needed.
• Placing the step first ensures that the flaky Playwright/browser step cannot prevent author assignment from running.
• Re-running on synchronize events is harmless since --add-assignee is idempotent when the user is already assigned.

Important Files Changed

Filename	Overview
.github/workflows/pr-automation.yml	Renamed from run-devin.yml; adds an author-assignment step using gh pr edit with env-var-isolated inputs, placed first so browser flakiness can't block it

_{Reviews (2): Last reviewed commit: "Add PR author assignment and generalize ..." | Re-trigger Greptile}