I have found the issue. The issue was in defining parameters correctly in boards.txt
Wow, if only someone had already looked through your boards.txt, found the problem, fixed it, tested it and submitted a pull request. Oh, that's right, I did that. Then instead of accepting my pull request, you deleted the repository, made the exact same change yourself, and completely ignored me. Then you also ignored me when I pointed out that your links were broken. If you don't want to say thanks or give me credit that's your choice but you could at least explain what was necessary to have the port of your board labeled to help others who may have the same problem in the future. Because of what you did they can't even look at the pull request I submitted. You didn't even take a second to let me know that my fork of your crappy repository is now pointless so that I can delete it. I took time out of my day to try to help you out because I believe in open source and giving back to the Arduino community. It's people like you who make me want to give up on that and just be selfish, like you. There are plenty of other things I could have spent that time on.
So, because unlike you I do believe in giving back to the Arduino community, here's an explanation of what needs to be done to get a board's port to be labeled with the board name in the Arduino IDE Tools > Port menu:
This can only be effectively done for boards that have a unique VID/PID. If your board uses a USB-serial chip (such as FT232, CH340, etc.) with the standard VID/PID it won't be useful because other different boards will also have the same VID/PID.
In the boards.txt entry for the board you must define the VID and PID of the board:
if the board is available with multiple VID/PIDs you can define all of them:
After adding these definitions in boards.txt (and restarting the Arduino IDE if it was running) you will see the board name defined in boards.txt listed after the port name in the Port menu, e.g. COM4 (Board Name).
Note that you should not confuse the above definitions with the build.vid/build.pid properties which may also be defined in boards.txt e.g.:
If you want helpful Tools > Port menu labels for boards using standard USB-serial chips with generic VID/PIDs you may be interested in a little something I wrote that does just that: