build.json file is not saved
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git, javascript
Research direction
Inspect commit f2753f8 to find the code that previously saved build.json, then run the npm run last example to reproduce the console-only behavior. Restore the expected file-saving behavior and verify that build.json is created with the last commit information.
Written by the indexing model from the issue text.
Description
Looks like f2753f8 commented out the code that saves a build.json file, meaning the example with npm run last only produces console output unless you specifically install 0.2.3 or earlier.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 2
- 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 bahmutov/last-commit
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
bahmutov/last-commit#5 ·
All issues in bahmutov/last-commit
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Add: BuyPass TV Openchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·