github-issue-tower-defence-management 1.147.4 → 1.148.0

package/.github/workflows/umino-project.yml

@@ -101,6 +101,18 @@ jobs:
 
           echo "Resolved ITEM_ID=$ITEM_ID"
 
+          if [ "${{ github.event.action }}" = "opened" ]; then
+            EXISTING_STATUS=$(gh api graphql \
+              -f query='query($itemId:ID!){node(id:$itemId){... on ProjectV2Item{fieldValueByName(name:"Status"){... on ProjectV2ItemFieldSingleSelectValue{name}}}}}' \
+              -f itemId="$ITEM_ID" \
+              --jq '.data.node.fieldValueByName.name // ""')
+
+            if [ -n "$EXISTING_STATUS" ]; then
+              echo "Status is already $EXISTING_STATUS; keeping it instead of overwriting with ${{ env.unread }}"
+              exit 0
+            fi
+          fi
+
           gh api graphql \
             -f query='mutation($projectId:ID!,$itemId:ID!,$fieldId:ID!,$optionId:String!){updateProjectV2ItemFieldValue(input:{projectId:$projectId,itemId:$itemId,fieldId:$fieldId,value:{singleSelectOptionId:$optionId}}){projectV2Item{id}}}' \
             -f projectId="$PROJECT_V2_ID" \

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+# [1.148.0](https://github.com/HiromiShikata/npm-cli-github-issue-tower-defence-management/compare/v1.147.5...v1.148.0) (2026-08-09)
+
+
+### Features
+
+* **core:** assign manager to allow-listed authors' pull requests that are not project items ([#1467](https://github.com/HiromiShikata/npm-cli-github-issue-tower-defence-management/issues/1467)) ([7d2a606](https://github.com/HiromiShikata/npm-cli-github-issue-tower-defence-management/commit/7d2a606e453b957578fdf75987974f6d8e5458c4))
+
+## [1.147.5](https://github.com/HiromiShikata/npm-cli-github-issue-tower-defence-management/compare/v1.147.4...v1.147.5) (2026-08-09)
+
+
+### Bug Fixes
+
+* **console:** render cross-repository issue references with the referenced repository ([#1462](https://github.com/HiromiShikata/npm-cli-github-issue-tower-defence-management/issues/1462)) ([d415451](https://github.com/HiromiShikata/npm-cli-github-issue-tower-defence-management/commit/d415451727639a8f23bbcb44e4153184748fea0d))
+
 ## [1.147.4](https://github.com/HiromiShikata/npm-cli-github-issue-tower-defence-management/compare/v1.147.3...v1.147.4) (2026-08-09)
 
 

package/README.md

@@ -216,6 +216,8 @@ labelsNotRequiringPullRequest?: string[] | null # Optional: List of issue labels
 changeTargetPathAliases?: Record<string, string> | null # Optional: Map of short alias keys to full repository-root-relative directory paths, for use with `change-target:<alias>` labels. Allows deeply nested paths that exceed GitHub's 50-character label limit to be referenced via a short alias. Example: `{ "adapters": "src/domain/usecases/adapter-interfaces" }` — a label `change-target:adapters` then matches files under `src/domain/usecases/adapter-interfaces/`. Keys not matching any `change-target:` label value are ignored; values with leading or trailing slashes are normalized automatically. Declared at the top level (sibling of startPreparation), not inside it.
 claudeCodeOauthTokenListJsonPath?: string # Optional: Path to a JSON file listing long-term Claude Code OAuth tokens to rotate across (see "Claude OAuth Token Rotation" below). Declared at the top level (sibling of startPreparation), not inside it.
 autoAssignManagerAuthors?: string | string[] | null # Optional: Restrict which authors' open, unassigned issues and pull requests are auto-assigned to the manager. Accepts a comma-separated string or an array of GitHub author logins (bot logins carry the `[bot]` suffix, for example `renovate[bot]`). When set to a non-empty list, only items whose author is in the list are auto-assigned; when omitted, null, or empty, every open unassigned item is auto-assigned (current behavior). Author matching is exact equality. Declared at the top level (sibling of startPreparation), not inside it.
+queryToAddProjectEnabled?: boolean # Optional: Enable the queryToAddProject search (default false). The search runs only when this is true, so setting queryToAddProject alone changes nothing. Declared at the top level (sibling of startPreparation), not inside it.
+queryToAddProject?: string | null # Optional: GitHub search query string, used only when queryToAddProjectEnabled is true. Each schedule cycle, issues and pull requests matching this query that are not already on the project board are added to the project and, when their author satisfies autoAssignManagerAuthors, assigned to the manager. Omit or set to null to skip this search. Declared at the top level (sibling of startPreparation), not inside it.
 dailySecurityScan?: # Optional: Run a daily OSV-Scanner security scan across locally cloned repositories of the org. Declared at the top level (sibling of startPreparation).
   scanBaseDirectory: string # Base directory searched (4 levels deep) for cloned repositories to scan
   targetHourUtc: number # UTC hour (0-23) at which the scan runs once per day; the scan runs only when a target date matches this hour at minute zero
@@ -286,6 +288,8 @@ maximumPreparingIssuesCount?: number # Optional: Max concurrent preparing issues
 utilizationPercentageThreshold?: number # Optional: 5-hour utilization hard threshold (percentage, default 90). Tokens at or above this value are excluded from rotation
 allowedIssueAuthors?: string # Optional: Comma-separated list of allowed issue authors
 autoAssignManagerAuthors?: string # Optional: Comma-separated list of author logins whose open, unassigned issues and pull requests are auto-assigned to the manager. When set to a non-empty list, only items whose author is in the list are auto-assigned; when omitted or empty, every open unassigned item is auto-assigned (current behavior). Author matching is exact equality; bot logins carry the `[bot]` suffix (for example `renovate[bot]`)
+queryToAddProjectEnabled?: boolean # Optional: Enable the queryToAddProject search (default false). The search runs only when this is true, so setting queryToAddProject alone changes nothing
+queryToAddProject?: string # Optional: GitHub search query string, used only when queryToAddProjectEnabled is true. Each schedule cycle, issues and pull requests matching this query that are not already on the project board are added to the project and, when their author satisfies autoAssignManagerAuthors, assigned to the manager. Omit to skip this search.
 thresholdForAutoReject?: number # Optional: Consecutive rejections before escalation (default: 3)
 workflowBlockerResolvedWebhookUrl?: string # Optional: Webhook URL. Supports {URL} and {MESSAGE} placeholders
 preparationProcessCheckCommand?: string # Optional: Shell command template with {URL} placeholder to check if a preparation process is alive. Orphaned Preparation issues (process exits non-zero, or stale aw log) are evaluated for completion: if work is done they advance to Awaiting Quality Check; otherwise an `Auto Status Check: REJECTED` comment is posted and the issue falls back to Awaiting Workspace, except that once `thresholdForAutoReject` cumulative orphan-time rejections accumulate within the recent comment window (and no earlier escalation marker is present) the issue is transitioned to Failed Preparation instead