Clarify PR-to-project linking requires manual action

[Copilot]

The workflow documentation incorrectly implied PRs are automatically added to the "Blog: coreydaley.dev" GitHub Project. Only issue closure on PR merge is automated (via .github/workflows/close-issue-on-pr-merge.yml).

Changes

Updated .github/copilot-instructions.md:

• Added explicit step 3: "Add PR to Project" with three methods:
  • GitHub CLI: gh pr edit <PR-number> --add-project "Blog: coreydaley.dev"
  • GitHub API
  • Web UI sidebar
• Renumbered subsequent steps (3→4, 4→5, 5→6)
• Updated project status flow diagram to show [Manual: Add to Project] step
• Added CRITICAL callout in "Pull Request Best Practices" section
• Applied same clarifications to "Content Creation Workflow" section for consistency

Before/After

Before:

PR is automatically added to the project in "In Progress" status

After:

Manually add the PR to the "Blog: coreydaley.dev" project
Methods to add PR to project:
  - Method 1 (GitHub CLI): Use `gh pr edit <PR-number> --add-project "Blog: coreydaley.dev"`
  - Method 2 (GitHub API): Use the GitHub API to add the PR to the project
  - Method 3 (Web UI): In the PR sidebar, click "Projects" and select "Blog: coreydaley.dev"
This step is NOT automatic

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.