mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1369] act git module fails process repos that use .git/packed-refs #728
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#728
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @Josverl on GitHub (Oct 1, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1369
Bug report info
Command used with act
Describe issue
act reports errors getting the git ref and git revision,
and hangs on the associated cleanup tasks at the end of the job(s)
the used git module appears to be assuming thet the gist refs are in a simple format , and do not process the '.git/packed-refs'
When repository histories start getting really long, having hundreds of tags starts to slow things down, so git pack-refs will put them all in the packed-refs file.
Link to GitHub repository
https://github.com/Josverl/micropython-stubs
Workflow content
Relevant log output
Additional information
the same issue is seen with almost all workflows in this and other repos in which
git pack-refshas been used.@Josverl commented on GitHub (Oct 1, 2022):
it may be better to use
it show-ref refs/heads/<branch>,or to enhance the algorithm in
func FindGitRevisionto.git/refs/heads/<branch>/HEADfiles@github-actions[bot] commented on GitHub (Nov 3, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@AlexRuiz7 commented on GitHub (Nov 25, 2022):
Facing the same problem here.
@Josverl were you able to find a solution?
@Josverl commented on GitHub (Nov 26, 2022):
No, not really
The only dirty workaround is to create a copy of the repo without packed refs and then trying to keep that up to date
My go skill are read-only