feat(deploy): add option to 'deploy' command to show uploaded files
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start at the deploy command's option handling and existing json output path. Trace how uploaded files are collected and represented, then add a deploy option that includes them when combined with json. Done means the uploaded file list is present in parseable JSON output and existing deploy output remains unaffected.
Written by the indexing model from the issue text.
Description
Which problem is this feature request solving?
When the deploy command runs, it doesn't show what files have been uploaded to Netlify. Knowing what these files are would help in case post-processing is needed.
Describe the solution you'd like
Add an option to the 'deploy' command that will show the uploaded files, if combined with the json option to making the output parseable by a post-processing command.
Pull request (optional)
- I can submit a pull request.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 476
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 54
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from netlify/cli
-
netlify dev returns 403 for static files in subdirectories on Windows (backslash in rewritten path)Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
`client-ip` is not an IP address when `x-forwarded-for` holds a list or a portPossibly taken @Dev-next-gen claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
`netlify dev` with `--cwd` from outside the project: every function 500s with "module is not defined in ES module scope" (`detectZisiBuilder` passes a string to `readPackageUp`)Possibly taken @bsplatt92 claimed this 48 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area: command: deploy area: docs type: feature
Difficulty 1/5 Under an hour Newbie friendliness 88/100
netlify/cli#1984 · 19 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
netlify/cli#8522 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:session-state issue-rating: 🌊 off-meta tidepool P2
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openclaw/openclaw#165245 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
agent-canvas bug priority:low ready-for-dev
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
spicetify/marketplace#1262 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 68/100
Maintainers usually reply within 1 day