PowerShell / PowerShell/PSResourceGet
Publish-PSResource should skip some files (new parameters)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature / enhancement
Maybe I have already tired everyone, but I still insist that the new version should not break its behavior relative to the old one.
The v2 version skipped hidden files and folders, the v3 does not (since I cannot re-open #888, I published new issue)
It seems to me that by default, they should still be skipped.
And even better, there should be a special set of parameters that allows you to specify what exactly to skip.
Here are examples of unsuccessful, in my opinion, publications of modules that have the entire contents of the .git folder.
https://www.powershellgallery.com/packages/RunAsUser
https://www.powershellgallery.com/packages/GitLabProvider
https://www.powershellgallery.com/packages/dockeraccesshelper
https://www.powershellgallery.com/packages/SEPPmail365cloud
And here is an example where there is no .git folder, but there is .vscode and .github
https://www.powershellgallery.com/packages/PowerShellForGitHub
Among the examples shown there are quite popular modules (above 4.5 millions of downloads) and publishing them in this form reduces the quality of the community.
Proposed technical implementation details (optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Publish-PSResource entry point and reproduce publishing modules containing .git, .vscode, and .github, comparing the reported v2 and v3 behavior. Clarify the default exclusions and the proposed parameters before identifying the relevant tests; done means default skipping preserves the expected behavior and explicit exclusions are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100