How to remove manisfest from log ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- ci-cd
Research direction
Start at index.js around line 89 and reproduce the GitHub Action behavior that downloads manifest.json and prints its contents. Check how curl errors are currently surfaced, then verify that successful downloads no longer emit the manifest while error cases still expose the downloaded content. Confirm the result using an action run or the repository's available tests.
Written by the indexing model from the issue text.
Description
The file https://deployer.org/manifest.json is downloaded and the content is shown in logs, 860 lines...
I don't think it's possible to hide content currently: https://github.com/deployphp/action/blob/v1.0.23/index.js#L89.
In case of a curl error, keeping the log is valuable, I think.
What would be the right approach to fix the problem ?
Idea:
- Save manifest.json in file with curl option --output
- If no error parse it
- In case of error show the content file
Upvote & Fund
- We're using Polar.sh so you can upvote and help fund this issue.
- We receive the funding once the issue is completed & confirmed by you.
- Thank you in advance for helping prioritize & fund our backlog.
- Dominant language
- TypeScript
- Stars
- 269
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 deployphp/action
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Puzzling ssh fail Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in deployphp/action
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100