nope, still happens with the latest Node 10 release.
yes, this is the great tragedy of our times! put some pressure on the major git hosting providers to allow browsers to interact directly
@wmhilton it turned out to be a relatively minor change to get the Antora tests working with isomorphic-git 0.65. Antora itself doesn't read the index, so it was just the test helper that needed the update. See https://gitlab.com/antora/antora/merge_requests/357/diffs#diff-content-5dfaa498c615742430124be386a49b71c6895fa9
Hi... I'm having a problem pushing on Node (with no URL but a dir). I'm getting a
RemoteUrlParseError error as a result of the fact that config() get a URL of this format: git@github.com:brettz9/update-packages.git which is not understood by parseRemoteUrl (called via GitRemoteManager.getRemoteHelperFor) as the regex it expects is /(\w+)(:\/\/|::)(.*)/ which the git@ type URL doesn't fit. I suppose I can convert it with github-url-converter but thought it should be handled within. File an issue?
I'm assuming I'm doing something wrong..
There is chrome extension that allow to disable CORS checks (actually it enable cors headers for every request) you can check if it's open source and if yes check it's source code how it was implemented, if it's not open source you can ask on StackOverflow how to enable CORS in chrome extension
Not sure if it will work with fetch but chrome extension can add permission to url https://developer.chrome.com/extensions/xhr#requesting-permission if you want access git hosting like GitHub or GitLab there should be no problem
I'm using isomorphic-git in a browser extension, and I'm a bit confused about security with respect to authorization. I know storing passwords/access tokens in plaintext on a server-side application is a very bad idea, but is the same thing true for doing it within the user's own browser?
@jonahnewman Storing user credentials in client-side storage (such as localStorage or IndexedDB) can be OK as long as your site has no third-party script tags running on it which might try to steal the credentials. The best solution is to use the browser's own Credential Management API - the downside of that being it's poorly supported at the moment (https://caniuse.com/#feat=credential-management)
somehow
import { GitError } from 'isomorphic-git/internal-apis'; seems to fail
Question: I'm trying to pull/fetch on an existing repo that works great from the console, but I'm getting a 401 from within my app. I suspect (because the error is 401, and it's bitbucket) that this is because my (non-standard) key for bitbucket isn't being loaded. How does one solve this?
That's what my repo currently uses, at least.
So what I was looking at was seeing if it's possible to configure isomorphic-git (currently, if not, I will add it) to be able to specify a username + a public key? I know I can go the token route, however for the workflow I intend for my app, that is obviously not ideal.
The 401 emerges when I override the imported git url with an
https:// style formatted URL. Because the id_bitbucket isn't the default .ssh key for <whatever part of the system electron-bundled nodejs imports from>.
Otherwise, I'm deeply in love with this project for making it so simple to manipulate git's object graph.
but regardless of that, I need an app-configurable method of importing a private/public keypair and using it for authentication for pulling.
Hi, I hope someone can help, perhaps I'm just doing something wrong. I need the equivalent of
git checkout -b branch-name, and I thought the branchcommand with checkout: true would give me what I wanted (a new branch at the same commit as the branch I just switched from), but it doesn't
The scenario is: I've created a remote repo, I clone it , create a bunch of files on
master, commit these changes and push them to the remote, then attempt to checkout a new branch.
The result is that the new branch only has the initial commit; i.e. it's in the same state that the master branch was at the point that it was cloned. The latest commit isn't present. The files are there, but they're all treated as new
Am I using the wrong command (
checkout/fastCheckout seem to depend on the remote branch existing already) or is there no equivalent of git checkout -b ...?
Uncaught (in promise) TypeError: Cannot read property 'byteLength' of null
at Function.wrap (background.bundle.js:19065)
at hashObject$1 (background.bundle.js:28127)
at getWorkdirOid (background.bundle.js:28485)
at async Module.status (background.bundle.js:28524)
at Function.wrap (background.bundle.js:19065)
at hashObject$1 (background.bundle.js:28127)
at getWorkdirOid (background.bundle.js:28485)
at async Module.status (background.bundle.js:28524)
This makes me think that I'm giving it bad arguments, but I've checked and i'm sure they're correct. Is there some other possible explanation?
I'll be working on it again this morning and will let you know if I make any progress.