Revert "Remove unnecessary workflow"

[haacked]

This reverts commit 70920f3.

[greptile-apps]

PR Summary

Restores the call-flags-project-board.yml workflow for automated feature flag project board management in .github/workflows/. This workflow integrates with PostHog's centralized project board system for tracking feature flag implementations.

• Re-adds workflow that triggers on PR events (open, review, sync) to update feature flag project board
• Leverages shared workflow from PostHog/.github repository for consistent project management
• Maintains automation for tracking feature flag development across PostHog repositories

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

Re-adds call-flags-project-board.yml workflow, completing the feature flag project management setup alongside existing workflows like main.yaml and stale-labeller.yaml. This maintains consistency in PostHog's CI/CD pipeline.

• Workflow complements existing CI setup which already includes build, test, format, and release processes
• Fits into repository's established GitHub Actions pattern of using reusable workflows
• Aligns with repository's automated project management approach seen in stale-labeller.yaml

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

Reintroduces the feature flag project board workflow file, examined in context with the repository's comprehensive CI/CD setup documented in .github/workflows/main.yaml and stale-labeller.yaml.

• Integration extends the repository's existing automation ecosystem that includes build, test, and stale PR management
• Workflow specifically runs on pull request lifecycle events to maintain feature flag development tracking
• Uses established pattern of calling reusable workflows from PostHog's central .github repository

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

Reversion of workflow removal maintains critical cross-repository orchestration for feature flag tracking in PostHog's ecosystem.

• Restores .github/workflows/call-flags-project-board.yml that serves as a lightweight workflow caller, keeping infrastructure code minimal
• Ensures continued compatibility with PostHog's unified feature flag tracking system across multiple SDKs
• Follows the repository's consistent pattern of externalizing shared workflows to reduce maintenance overhead

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

Re-adds critical project board workflow file that was previously removed, completing the repository's CI/CD automation infrastructure by maintaining integration with PostHog's centralized feature flag tracking system.

• Re-added file acts as a bridge between .NET SDK and central PostHog project management, triggered by PR lifecycle events
• Notable for its inheritance of secrets configuration, enabling secure cross-repository workflow calls
• Special attention to draft PR handling, with explicit draft status parameter passed to central workflow

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

Restores the call-flags-project-board.yml workflow, which works in conjunction with the repository's existing GitHub Actions infrastructure (main.yaml and stale-labeller.yaml) documented in the codebase.

• Workflow operates alongside scheduled jobs (like stale PR checking at midnight UTC) without scheduling conflicts
• Aligns with repository's existing permissions model which already includes PR write access for automation
• Maintains consistency with Ubuntu-latest runner environment used by other workflows

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

Reverts the removal of call-flags-project-board.yml workflow file, with analysis of the workflow's role in the CI/CD ecosystem.

• Cross-repository workflow inheritance requires specific GITHUB_TOKEN permissions, a critical security detail not previously highlighted
• File restoration fixes potential automation gaps in PR lifecycle events (opened, ready for review, synchronized)
• Completes the unified feature flag tracking system without interfering with existing 14-day stale PR checks

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}