mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #912] Issue: actions/checkout doesn't copy git tracked but gitignored files #543
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#543
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 @jsoref on GitHub (Dec 2, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/912
The general behavior of
.gitignoredoesn't prevent files that are tracked from being checked out. It just prevents from from being updated or added.I'd expect that act not copy over untracked files matched by
.gitignore, but I'd expect it to include tracked files that are matched by.gitignore.System information
act: catthehacker/ubuntu:act-latestactversion: 0.2.25Expected behaviour
Files listed in
.gitignoreshould be present in the checked out repositoryActual behaviour
Files listed in
.gitignoreare not presentWorkflow and/or repository
github.com/jsoref/ignored@bfbee7f061https://github.com/jsoref/ignored/runs/4398686247?check_suite_focus=true
github.com/jsoref/ignored@5e20813c26https://github.com/jsoref/ignored/runs/4398859601?check_suite_focus=true
Steps to reproduce
github.com/jsoref/ignored@bfbee7f061to a GitHub repogithub.com/jsoref/ignored@5e20813c26to the GitHub repoactoutputLog
@catthehacker commented on GitHub (Dec 2, 2021):
Have you tried
--use-gitignore=false?@jsoref commented on GitHub (Dec 2, 2021):
Yes, it would work, see the second commit/run.
But I shouldn't need to
@catthehacker commented on GitHub (Dec 2, 2021):
Right, we can't change behaviour because it will break functionality for other people
@jsoref commented on GitHub (Dec 2, 2021):
I see three possible behaviors:
.gitignore.gitignoreThe current default is 2. The flag gets 1. I'm looking for 3.
The distinction between 2 and 3 is imo a bug, hence this bug.
@github-actions[bot] commented on GitHub (Jan 2, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@jsoref commented on GitHub (Jan 2, 2022):
Please tag
@github-actions[bot] commented on GitHub (Feb 2, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@jsoref commented on GitHub (Feb 2, 2022):
It's still a thing...
@github-actions[bot] commented on GitHub (Mar 6, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@jsoref commented on GitHub (Mar 6, 2022):
It's still a thing...