Remove legacy update-project job builder - now handled by unified handler #13074
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Individual job builders for
update-projectandcreate-project-status-updateexisted but were never called in production. These safe outputs are processed by the unified project handler manager (buildProjectHandlerManagerStep) since the handler architecture consolidation.Changes
Removed dead code:
pkg/workflow/update_project_job.go- LegacybuildUpdateProjectJobfunction (92 lines)pkg/workflow/update_project_test.go- Tests for removed builder (328 lines)pkg/workflow/update_project_token_test.go- Token tests (121 lines)pkg/workflow/safe_outputs_integration_test.go- Removed update_project test caseRetained:
parseUpdateProjectConfig()inupdate_project.go- Still used by unified handlerparseCreateProjectStatusUpdateConfig()increate_project_status_update.go- Still used by unified handlerContext
The unified project handler manager in
compiler_safe_outputs_steps.gohandles all project-related safe outputs:The individual job builders were orphaned when this architecture was introduced but never cleaned up.
Original prompt
💡 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.