fix: after git clone for remote git actions & workflows, don't immediately git fetch repeating same work #1164
No reviewers
Labels
No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
run-multi-platform-tests
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner!1164
Loading…
Reference in a new issue
No description provided.
Delete branch "mfenniak/forgejo-runner:fix-double-fetch-on-repo-init"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
(Stacked on #1162 --
78b2252097is the only relevant commit to this change)Small optimization for when a repo cache is initialized to not
clonethenfetch.fetchstill occurs usually.git clonefor remote git actions & workflows, don't immediatelygit fetchrepeating same workcascading-pr updated at actions/setup-forgejo#766
fix: afterto fix: aftergit cloneis successful, don't immediatelygit fetchrepeating same workgit cloneis successful for a step/reusable workflow, don't immediatelygit fetchrepeating same workfix: afterto fix: aftergit cloneis successful for a step/reusable workflow, don't immediatelygit fetchrepeating same workgit clonefor remote git actions & workflows, don't immediatelygit fetchrepeating same workNeeds revision (if possible) as the fetch provides value in getting the non-default-branch references from the remote, even just after the clone.
Pull request closed