Added symlinks option to the copy plugin
Metadata
Current evaluation
Closed without merging. Maintainer declined the symlink option, proposing a complete redesign of the copy plugin's symlink handling instead. Contributor was invited to reopen or submit a new PR if they wish to implement the proposed approach.
Suggested action: —
No scores available.
Issue body
We need this change since we need to copy large directories.
Please, consider adding this change to your codebase.
Thank you,
Renat
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without merging. Maintainer declined the symlink option, proposing a complete redesign of the copy plugin's symlink handling instead. Contributor was invited to reopen or submit a new PR if they wish to implement the proposed approach. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging. Maintainers declined the symlink option, planning instead to redesign the copy plugin's symlink handling logic entirely. Contributors were asked to reopen or submit a new PR if they wish to continue development under the new approach. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The symlinks option PR for the copy plugin was closed. Maintainers rejected it, preferring a complete plugin redesign to handle symlinks automatically. The contributor was invited to reopen or submit a new PR. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1004 fix: [PROTOTYPE] add option to use symlinks with the npm plugin | craft-parts | closed | Closed without merging. The pull request adding a symlink option for the npm plugin was abandoned due to prolonged inactivity and lack of reviewer engagement. No code changes were integrated. |