Hi! Thanks for the pull request. Please ensure that this change is linked to an issue by mentioning an issue number in the description of the pull request. If this pull request would close the issue, please put the word 'Fixes' before the issue number somewhere in the pull request body. If this is a tiny change like fixing a typo, feel free to ignore this message.

@samcoe oh, excuse my lack of insight, I wonder why my PR commit message is missing, it surprises me.

The makefile function is too simple. As the first step of my contribution to cli, I should make more people happy to use the makefile. In the first stage of contribution, I want to continue to enrich the makefile, don't you think?

Hi, I'm trying to untangle what happened here, but I think you opened a PR from the trunk branch in your fork, but then the “Pull” bot had reset your trunk branch and thus effectively erased the contents of this PR. Afterwards, GitHub erroneously thought that this PR was merged and marked it as such. However, none of your changes got merged.

Nevertheless, I have reviewed your originally proposed changes at cubxxw@f9dad36 and even though I can see how a better-documented Makefile is nice to have, the solution is somewhat hacky and I don't think we want to maintain it, especially since the "standard" make commands (make, make test, make install, make clean) should be self-evident, and all the other ones should only be used by our team and not by outside contributors.

For your future PRs, please disable the Pull bot on your account resetting branches that you have opened PRs from.