is there a way to get the tree hash of a particular ref (tag)?
@asymmetric off the top of my head, all I can think of is
M-: (magit-rev-hash "HEAD")
Yep, GitLab has my public gpg key.
I have had a few entries in my authinfo.gpg,
machine gitlab.com/api/v4 login username^forge password TOKENworks for forge stuff and machine gitlab.com login port 443 username password TOKEN which 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.
Oh, i think i finally got it. I moved the entry before the one for forge
also stripped the port from the line
Is there a setting to have messages wrap in the magit log buffer or have refnames show on a subsequent line? Took a look thru the docs but couldn't find anything. My problem is that the initial line of a commit message/branch names can be long so I can't see both commit msg & branch name (refnames) at the same time
You can see the refname cannot be fully seen (latest commit)
Its only when I increase window width it can be seen
Not sure if the log view has the ability to wrap this if window width is too small or any hints on how I could add this feature?
Hi,
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.
@dyereh You can additionally hide the right margin to get more space for the other information using
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.]
@innerout It already does but you have to enable it like so: https://magit.vc/manual/transient/Enabling-and-Disabling-Suffixes.html. Thanks for the hint about
--preserve-merges being deprecated.
Hello,
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.
Removing
.emacs.d/elpa/magit-20200517.1537/ so that it gets rebuit on startup fixed the issue for me.
Is there a way to create a new repository on GitHub with Magit, if you only have a local git repository? With forge, I can create a fork of an existing remote repository on GitHub. I don't understand how to create a completely new repository from just a local git repository. Am I missing something? I am able to get and create issues, fork an existing remote repository and create a PR https://practicalli.github.io/spacemacs/source-control/magit/forge.html
I got Magit forge working eventually, I found the official docs a bit hard to follow some times and also new to using gpg, so I wrote this guide to setting up forge using a gpg encrypted authinfo file https://practicalli.github.io/spacemacs/source-control/forge-configuration.html
What's a good way to ensure the output of a git hook gets printed out ?