changelog command never outputs anything
See original GitHub issueThe problem
Whenever I run the command changelog
, nothing is ever outputed. Be it having the file not empty, having a pending version change or a newly changed version, after publishing, etc.
Expected behavior
I’m not sure… what is the command even supposed to do? I excpect it to append an entry to the changelog file, if there is none yet for the current version. Aka I expect the publish
command to be a combination of version
, changelog
and pushing the commit/tag everywhere (git, pypi, etc.).
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Why would git log/status return no output? - Stack Overflow
Nothing. An empty line and back to the command-prompt. I would only get responses when I was in the parent directory, which was...
Read more >Is there a Unix command to record changes to output of ...
I don't know about a dedicated command, but I would have written something like that: (while true; do sleep 0.1; showst; done) |...
Read more >Why does this 'at' command not print to the standard output?
My question is, in the following sample bash script that I have created, why is "Running" never -- as far as I can...
Read more >Pre-command output to Commvault job log | Community
I have successfully set up a pre-scan command and it does what I want. ... was the Pre-Scan phase hung and the command...
Read more >ctest(1) — CMake 3.25.1 Documentation
Build the software by running a command in the build tree. Record the build output log and detect warnings and errors. See the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There was a problem with the merge and the commit history was all crapped. This now seems to be fine, I will follow the other linked issues for more details or solutions if it ever happens again.
Yes, I just found that issue, as you say I changed
version_source = 'commit'
and all fixed.