Fix "Item not found with ID" error for assigned trigger by adding auto_add parameter

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)

[Copilot]

When using the issues trigger with assigned event type, users encountered "Item not found with ID" errors when passing github.event.issue.node_id or github.event.issue.id as the content_id. This occurred because the issue exists but isn't in the project yet when the assignment event fires.

Problem

The action expected issues/PRs to already be in the project, but the assigned trigger often occurs before items are manually added to projects. This resulted in the following error pattern:

# This workflow would fail with "Item not found with ID"on:
issues:
types: [assigned]jobs:
update-project:
steps:
- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todo

Solution

Added an auto_add parameter (default: false) that automatically adds issues/PRs to the project if they're not already in it. When enabled, the action:

1. Detects when an issue/PR exists but isn't in the specified project
2. Uses the addProjectV2ItemById GraphQL mutation to add it to the project
3. Proceeds with the field update as normal

Usage

- uses: github/update-project-action@v2with:
content_id: ${{ github.event.issue.node_id }}field: Statusvalue: Todoauto_add: true # Automatically add issue to project if not already in it

Changes

• New auto_add input parameter with backward-compatible default (false)
• addProjectItem() function using GitHub's Projects V2 API
• Enhanced error detection to distinguish between "item doesn't exist" vs "item not in project"
• Comprehensive test coverage including full workflow simulation
• Documentation and examples for the assigned trigger use case

Also fixed a case sensitivity bug in convertValueToFieldType() that was causing number field conversions to fail.

The solution maintains full backward compatibility while enabling the assigned trigger workflow that was previously failing.

Fixes#55.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[benbalter]

@copilot can you fix the failing tests?

[Copilot]

@copilot can you fix the failing tests?

Fixed the failing tests! The issue was a case sensitivity problem in the test cases. The tests were expecting uppercase "NUMBER" but the actual implementation uses lowercase field types. Updated the tests to use "number" (lowercase) to match how field types are processed in the code. All 33 tests now pass with 100% line coverage. (commit 521b015)