9.0.0: Versioning control: not able to pull and/or push

When I commit and I try to push or to pull, I’m not able.
Where can I setup or change the parameters?

image

image

Does this thread help any ?

1 Like

It should but not really because it seems ppl still have probleem.
Also the fact you need to go to generate the SSH key and all these stuff it’s not practical at all and the last message show that still not working as expected).

Settings should be way easier and intuitive
SSH keys (if required) should not be for nerds -only but should be friendly accessible by anyone.

So:

  • missing instructions
  • cumbersome to use
  • not intuitive
  • very difficult to make it work
  • needles feature, when implemented the way it is.

I hope we have not to wait 1 or 2 or even 3 years to get this:

  • working
  • user friendly

However I will link this post on that thread to keep this issue in one place

2 Likes

There have been several Git related commits to what will be 9.0.1 in Testing, in the last few days.
Try this.

1 Like

Same result and there is not any way to add/change GitHub account … zero … nothing.

How can be called “feature” this half-thing ?

  • No instructions
  • Cumbersome
  • Returns only issues
  • Not manageable
  • Everyone has issues but it seems there is not any solution. Isn’t it better to remove it?
    image
1 Like

You might consider that this is free software, written primarily by volunteers. Git integration is new in this version, and there are rough edges - which are actively being worked on.

I’d just advise that perhaps your choice of language isn’t the most supportive to those working on the project.

8 Likes

it’s not supportive neither to release a feature that ipso-facto is not working.
The situation it is as I described (wanted or not) and in my view not working features should be not included in an official release till the moment they are working.
I do not mean: with any bug. Because everything can have some bug with some extent.
But this is really not working as one, that uses the software, expects do.

It’s working just fine for some users, and others are finding this issue. Developers can’t test every single permutation of git repository, authentication method, and platform versions. We issued a number of release candidates for v9, did you test these out and report bugs?

1 Like

Lets take a step back before this bunfight turns nasty.

This is a great feature and I am soo please to see it integrated. Can I fully use it? no :frowning:
Right now the git status indicators are more useful than anything and Iwill drop to a command prompt todo the staging, commits, pushing and thus this feature isn’t blocking my workflow

my home gitea server is http and so the git push/pull doesn’t work as it won’t work via http :frowning: shame as almost all my gitea are on my private server (non-exposed so why https…)
Likewise it won’t work on my work gitea instance even though that is via https as it is SSO :frowning: but I can still use git.

My honest opinion is some of the git features integrated is removing the general git flexibility of git and that is via the git-credential-manager. Simply specifying the clone url should force the git credential manager to kick into life for authentication (UI popup on windows, unsure on linux since I use gentoo and 99% of my time go via terminal)

Also here is the thing about git integration… Mathworks have had git integrated for about a decade and it is still FLAWED and co-incidentally in exactly the same area. Same with Segasi… corporate contracts running into the millions. Does it work for the majority of users? yes it does as a majority of test-cases got this working…

4 Likes

do you know where the credentials are stored for the git functionality? I cloned/mange my projects with “Git Desktop”. Now i want to setup an already existing project to work inside the KiCad env. to be able to push/pull the files, somewhere i need to place my credentials for the gitgub server… where can i paste them?

image

1 Like

If I remember correctly, I managed to get it work by running ssh-keygen.exe from terminal. It stores keys in some default location. See Generating a new SSH key and adding it to the ssh-agent - GitHub Docs.

1 Like