[PR #433] [MERGED] Fix "reference not found" error #1448

New issue

Closed

opened 2026-03-01 21:51:13 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 21:51:13 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/433
Author: @lufia
Created: 11/30/2020
Status: ✅ Merged
Merged: 1/12/2021
Merged by: @cplee

Base: master ← Head: fix-resolving-branch

📝 Commits (4)

c789d52 Fix "reference not found" error
d68cbd4 Merge branch 'master' into fix-resolving-branch
1b69a6e Merge branch 'master' into fix-resolving-branch
3bcd90b Merge branch 'master' into fix-resolving-branch

📊 Changes

1 file changed (+16 additions, -17 deletions)

View changed files

📝 pkg/common/git.go (+16 -17)

📄 Description

If an action uses the branch to pin the major version, for example - use: 8398a7/action-slack@v3
will stop with an error: "v3: reference not found."

In this case act should use refs/remotes/origin/v1 as a name to resolve v1 revision.

#311

I checked:

In b3299ecd30 (current master) stopped by - use: 8398a7/action-slack@v3
This patch fixed the above error.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/nektos/act/pull/433 **Author:** [@lufia](https://github.com/lufia) **Created:** 11/30/2020 **Status:** ✅ Merged **Merged:** 1/12/2021 **Merged by:** [@cplee](https://github.com/cplee) **Base:** `master` ← **Head:** `fix-resolving-branch` --- ### 📝 Commits (4) - [`c789d52`](https://github.com/nektos/act/commit/c789d5275c65e8bb7d4d755792549c1610c75fb5) Fix "reference not found" error - [`d68cbd4`](https://github.com/nektos/act/commit/d68cbd436172528aeaec6e8b77cd2d9ae8a310dc) Merge branch 'master' into fix-resolving-branch - [`1b69a6e`](https://github.com/nektos/act/commit/1b69a6e625d13074b84ed67eea9318523915f572) Merge branch 'master' into fix-resolving-branch - [`3bcd90b`](https://github.com/nektos/act/commit/3bcd90bdd744041171f79c7e29af69148052d636) Merge branch 'master' into fix-resolving-branch ### 📊 Changes **1 file changed** (+16 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `pkg/common/git.go` (+16 -17) </details> ### 📄 Description If an action uses the branch to pin the major version, for example `- use: 8398a7/action-slack@v3` will stop with an error: "v3: reference not found." In this case `act` should use **refs/remotes/origin/v1** as a name to resolve **v1** revision. #311 I checked: - In b3299ecd30bab3e69c92a04c96de1fb25863aa96 (current master) stopped by `- use: 8398a7/action-slack@v3` - This patch fixed the above error. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-01 21:51:13 +03:00

closed this issue
added the
pull-request
label

kerem referenced this issue

2026-03-01 21:53:23 +03:00

[PR #1448] [CLOSED] Add option for disabling DooD #1952

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1448

No description provided.

Rows
Columns