Remove undocumented view deletion attempts in campaign project creation

[Copilot]

GitHub's Projects v2 API doesn't officially support deleting or updating views. The previous implementation attempted to delete the default "View 1" after creating custom views using an undocumented GraphQL mutation, which would fail silently.

Changes

• Removed view deletion logic: Removed deleteProjectView() and deleteDefaultView() functions that used the undocumented deleteProjectV2View GraphQL mutation
• Simplified view creation: Configured views are now created as additional views without attempting to delete or modify the default "View 1"
• Updated documentation: Clarified that "View 1" remains and configured views are created as additional views

Research Findings

After verification of GitHub's API documentation:

1. No PATCH/PUT REST endpoint exists for updating ProjectV2 views
2. No documented GraphQL mutation exists for deleting or updating ProjectV2 views
3. The deleteProjectV2View mutation is not officially documented or supported

Implementation

// Create configured views as additional views
for (let i = 0; i < configuredViews.length; i++) {
  const viewConfig = configuredViews[i];
  await createProjectView(projectInfo.projectUrl, viewConfig);
}

// Note: GitHub's default "View 1" will remain. The deleteProjectV2View GraphQL mutation
// is not documented and may not work reliably. Configured views are created as additional views.

This approach works within GitHub's officially documented API capabilities. The default "View 1" remains in the project, and configured views are created as view #2, #3, etc.

Original prompt

Since we can't remove views, let's use update-project and rename the table default view1 in the project board to our board view in campaigns.

---

💡 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.

[mnkiefer]

@copilot Check that this graphql mutation actually exists.

[Copilot]

@copilot Check that this graphql mutation actually exists.

You're correct. After checking GitHub's API documentation, I found that:

1. No PATCH/PUT REST endpoint exists for updating ProjectV2 views
2. No documented GraphQL mutation exists for deleting or updating views
3. The original deleteProjectV2View mutation was also undocumented

The solution in commit 3c830d7 removes all view deletion/update attempts. GitHub's default "View 1" will remain, and configured views are created as additional views.