[Bug]: copyGitignored not working

Open
#159 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
tooling

Research direction

Start at the clone-repo path shown in the log and inspect how the copyGitignored setting from polyscope.json is handled after workspace creation. Reproduce on Windows 10 with copyGitignored enabled, then verify that Git-ignored files appear in the clone folder without the reported copy error.

Written by the indexing model from the issue text.

Description

Platform

Windows

Operating system version

Windows 10

System architecture

Intel (x86)

PolyScope Version

0.19.0.0

Bug description

I have copyGitignored set to true in polyscope.json. When I create a new workspace, it doesn't copy Git ignored files.

Steps to reproduce
  1. Create polyscope.json in the root of the project.
  2. Set copyGitignored to true.
  3. Create a new workspace.
  4. Visit the clone folder.
Relevant log output
[server] [clone-repo] [1722ms] git clone --no-local
[server:err] [clone-repo] Failed to copy gitignored files: 70 |             path: iss.path ? [${WE(W)}, ...iss.path] : [${WE(W)}]
Dominant language
No language data
Stars
20
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beyondcode/polyscope-community

All issues in beyondcode/polyscope-community

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.