by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Jonas Bernoulli
    @tarsius
    Yes you right.
    dyereh
    @dyereh
    Thanks for the help!
    SrAceves
    @SrAceves
    Hello
    is there a way to get the tree hash of a particular ref (tag)?
    asymmetric
    @asymmetric
    is there a way to show the hash of the current HEAD, without having to open magit status window?
    Kévin Le Gouguec
    @peniblec
    @tarsius Should I create an issue for the autoloading of magit-file-mode-map? (Whether the solution ends up being "moving the keybindings-only modes to another file", "banging on the autoload specs until they do TRT", or "document that one must (require 'magit-files))
    @asymmetric off the top of my head, all I can think of is M-: (magit-rev-hash "HEAD")
    Kévin Le Gouguec
    @peniblec
    @SrAceves not sure, but does (magit-rev-parse "REF:PATH") do what you want?
    Nick Anderson
    @nickanderson_gitlab
    Is there some difference between github/gitlab with respect to pushing and leveraging credentials stored in ~/.authinfo.gpg? I am able to push to my github repositories, but pushing to gitlab requires me to type my password each time.
    James Elliott
    @brunchboy
    Did you remember to add your public key on GitLab?
    Nick Anderson
    @nickanderson_gitlab
    Hum, perhaps not. I will check, but I wouldn't expect GitLab to need my public key for emacs to find the credentials in ~/.authinfo.gpg.
    Yep, GitLab has my public gpg key.
    James Elliott
    @brunchboy
    I don’t know then…
    Nick Anderson
    @nickanderson_gitlab
    Yeah, it's been plaguing me for quite some time. Strange and annoying. I will get it figured out one of these days.
    Noam Postavsky
    @npostavs

    Yep, GitLab has my public gpg key.

    Wasn't the question about public ssh key?

    Nick Anderson
    @nickanderson_gitlab
    Maybe it was. I should have indicated that I was cloning via https not ssh.
    Roland Everaert
    @montaropdf
    @nickanderson_gitlab, Did you define your gitlab instance in the alist forge-alist?
    Nick Anderson
    @nickanderson_gitlab
    I didn't, I am using gitlab.com and I do see that it's listed second in forge-alist (after github.com).
    Nick Anderson
    @nickanderson_gitlab
    mmm, it works for forge topics, but it's pushing that always prompts me for a pw. Maybe i am configuring the wrong thing.
    Noam Postavsky
    @npostavs
    Nick Anderson
    @nickanderson_gitlab
    Yeah i was just looking at my ~/.gitconfig I have same entries for github and gitlab credential sections. helper set to netrc -f ~/.authinfo.gpg -v
    Roland Everaert
    @montaropdf

    What is the format of your entry in .authinfo.gpg?

    Did you have a newline at the end as mentioned in the forge documentation?

    Nick Anderson
    @nickanderson_gitlab
    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.
    Jonas Bernoulli
    @tarsius
    The second entry is obviously wrong. 443 is not a valid key.
    Nick Anderson
    @nickanderson_gitlab
    Typo, I meant machine gitlab.com port 443 login username password TOKEN.
    Oh, i think i finally got it. I moved the entry before the one for forge
    also stripped the port from the line
    dyereh
    @dyereh
    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
    Jonas Bernoulli
    @tarsius
    (setq magit-log-show-refname-after-summary t) should help with that.
    dyereh
    @dyereh
    right - I had tried that. It does show the refname after summary as advertised but I'd like it to wrap if it doesn't fit in the column (often I have long 1st line commit messages (or long ref-names) Here's what I mean
    You can see the refname cannot be fully seen (latest commit)
    image.png
    Its only when I increase window width it can be seen
    image.png
    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?
    Roland Everaert
    @montaropdf

    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.

    Jonas Bernoulli
    @tarsius
    @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.]
    dyereh
    @dyereh
    @tarsius that's a fair point - for now toggle will be enough thx
    George Xanthakis
    @innerout
    Hello I would like to ask if magit will support --rebase-merges? I am using -preserve-merges a lot and there is a warning from git that it is deprecated.
    Jonas Bernoulli
    @tarsius
    @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.
    Roland Everaert
    @montaropdf

    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.

    George Xanthakis
    @innerout
    @tarsius Thanks and you are welcome.
    jvallon1
    @jvallon1
    When trying to load-library magit-margin, getting "Symbol’s value as variable is void: magit-margin-settings". But, if I eval-buffer, it loads. Just updated magit today from melpa
    jvallon1
    @jvallon1
    I did "byte-compile-file" on magit-margin, and it fixed it... odd...
    Nicolas Bock
    @nicolasbock
    Thanks for the hint jvallon1
    Removing .emacs.d/elpa/magit-20200517.1537/ so that it gets rebuit on startup fixed the issue for me.
    John Stevenson
    @jr0cket
    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
    Magnus Therning
    @magthe
    I don't think magit itself offers that, but there might be "companion packages" that do. I haven't seen it though. Personally I usually use the GitHub website for those steps. There are options though, like GitHub's own tool hub and Terraform.
    John Stevenson
    @jr0cket
    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
    Noam Postavsky
    @npostavs

    Create a file called ~/.authinfo
    Use SPC SPC epa-encrypt-file to encrypt the file with gpg.

    I think it should work to create ~/.authinfo.gpg right away, and it will encrypt when you save