@link-assistant/hive-mind 1.69.17 → 1.69.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +16 -0
- package/package.json +1 -1
- package/src/solve.repository.lib.mjs +6 -6
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,21 @@
|
|
|
1
1
|
# @link-assistant/hive-mind
|
|
2
2
|
|
|
3
|
+
## 1.69.18
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 9aa5659: Fix `--auto-fork` mode failing when continuing an existing fork PR whose
|
|
8
|
+
fork name already contained the upstream-owner prefix. `setupRepository`
|
|
9
|
+
in `solve.repository.lib.mjs` was applying the
|
|
10
|
+
`--prefix-fork-name-with-owner-name` option to `forkRepoName` (which is
|
|
11
|
+
the authoritative head repo name from the PR's `headRepository.name`),
|
|
12
|
+
producing a doubled prefix like
|
|
13
|
+
`konard/labtgbot-labtgbot-telegram-claude-agent` and a 404 lookup. The
|
|
14
|
+
prefix option now only controls fork _creation_, not fork _lookup_:
|
|
15
|
+
when `forkRepoName` is present, the expected fork is
|
|
16
|
+
`${forkOwner}/${forkRepoName}` and no alternate-name fallback is
|
|
17
|
+
attempted. Resolves #1803.
|
|
18
|
+
|
|
3
19
|
## 1.69.17
|
|
4
20
|
|
|
5
21
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -818,12 +818,12 @@ Thank you!`;
|
|
|
818
818
|
await log(`\n${formatAligned('🍴', 'Fork mode:', 'DETECTED from PR')}`);
|
|
819
819
|
await log(`${formatAligned('', 'Fork owner:', forkOwner)}`);
|
|
820
820
|
|
|
821
|
-
//
|
|
821
|
+
// Issue #1803: prefix flag controls fork CREATION; for lookup, trust forkRepoName from PR head data.
|
|
822
822
|
const headRepoName = forkRepoName || repo;
|
|
823
823
|
const standardForkName = `${forkOwner}/${headRepoName}`;
|
|
824
824
|
const prefixedForkName = `${forkOwner}/${owner}-${headRepoName}`;
|
|
825
|
-
const expectedForkName = argv.prefixForkNameWithOwnerName ? prefixedForkName : standardForkName;
|
|
826
|
-
const alternateForkName = argv.prefixForkNameWithOwnerName ? standardForkName : prefixedForkName;
|
|
825
|
+
const expectedForkName = forkRepoName ? `${forkOwner}/${forkRepoName}` : argv.prefixForkNameWithOwnerName ? prefixedForkName : standardForkName;
|
|
826
|
+
const alternateForkName = forkRepoName ? null : argv.prefixForkNameWithOwnerName ? standardForkName : prefixedForkName;
|
|
827
827
|
|
|
828
828
|
await log(`${formatAligned('✅', 'Using fork:', expectedForkName)}\n`);
|
|
829
829
|
|
|
@@ -832,9 +832,9 @@ Thank you!`;
|
|
|
832
832
|
let forkCheckResult = await $`gh repo view ${expectedForkName} --json name 2>/dev/null`;
|
|
833
833
|
let actualForkName = expectedForkName;
|
|
834
834
|
|
|
835
|
-
if (forkCheckResult.code !== 0 && !argv.prefixForkNameWithOwnerName) {
|
|
836
|
-
// Only try alternate name if
|
|
837
|
-
//
|
|
835
|
+
if (forkCheckResult.code !== 0 && alternateForkName && !argv.prefixForkNameWithOwnerName) {
|
|
836
|
+
// Only try alternate name if --prefix-fork-name-with-owner-name is off AND we're guessing
|
|
837
|
+
// (forkRepoName authoritative → alternateForkName is null and no fallback is attempted).
|
|
838
838
|
forkCheckResult = await $`gh repo view ${alternateForkName} --json name 2>/dev/null`;
|
|
839
839
|
if (forkCheckResult.code === 0) {
|
|
840
840
|
actualForkName = alternateForkName;
|