M-: (magit-rev-hash "HEAD")
machine gitlab.com/api/v4 login username^forge password TOKENworks for forge stuff and
machine gitlab.com login port 443 username password TOKENwhich I was hoping would work for git push (but doesn't appear to). I didn't have a blank line at the end of the file, but adding one makes no difference.
My team and I are beginning to use sub groups in our corporate gitlab instance, unfortunately, it seems that forge doesn't support that functionality. I have noticed that the slash character
/ is url encode after the subgroup name in the repository url.
I can't show you an example, I am not on the same computer, unfortunately.
L L. Finally you can
M-x toggle-truncate-lines(like in any Emacs buffer) but the result will be hideous. [That's why we should make sure commit message summaries are fairly short -- sometimes there just isn't enough space to display something longer.]
The problem I report above is solved. In fact, it was due to a lack of update of the entry related to the repository, in the DB, after it has been moved to its new location. So forge was not able to reach the remote.
In the end their is no problem. Sorry for the noise.
.emacs.d/elpa/magit-20200517.1537/so that it gets rebuit on startup fixed the issue for me.