I am unable to push tags while using, https://isomorphic-git.org/docs/en/push.
Is there something I am missing?
Here is my snippet for push,
git.push({fs, http, dir: repo_path_on_local, remote: remote_name, ref: branch_name})
Good evening. I'm having some issues when trying to push new files, which are being added into a new sub-folder (using lightning-fs). Most likely im doing something wrong :). The idea is that after the repo is cloned, im creating a new sub-folder, creating new file there, commit and push. The whole process is running ok and can see the commit in GitHub but ... the new folder and file are not there (
0 additions and 0 deletions). Any advice on how to handle this? Thank you.
const dir = '/test-repo';
await fs.promises.mkdir(`${dir}/new_folder`)
await fs.promises.writeFile(`${dir}/new_folder/new-file.txt`, `# NEW FILE`)
await git.add({ fs, dir: `${dir}/new_folder`, filepath: 'new-file.txt' })
let status = await git.status({ fs, dir: `${dir}/new_folder`, filepath: 'new-file.txt' })
console.log(status) // "added" is returned
let sha = await git.commit({
fs,
dir,
message: 'Added new-file.txt',
author: { name: 'test', email: 'test@test.com' }
})
console.log(sha) // sha is returned. no errors
let pushResult = await git.push({
fs,
http,
dir,
url: 'https://username:token@github.com/user/test-repo',
})
console.log(pushResult) // "ok" is returned. can see the commit in GitHub but 0 files are added/changed
I don’t think it’s possible to use isomorphic-git where merges are required. Workarounds we use: (1) try to make sure pushes/pulls happen often (that reduces the possibility of merge conflicts), (2) structure data and workflows such that multiple users are unlikely to concurrently modify the same object
We also plan on offering users an UI to perform a manual merge (by checking out both versions and showing a nice diff)
Ideally if pushes/pulls happen all the time continuously in background this should be less of an issue, but for some reason Git operations cause significant UI lag in our Electron app, even though they happen in the main thread (currently upgrading to latest isomorphic-git to see if that addresses it, and will look into background Node workers as well)
I need help with getting started with https://isomorphic-git.org/
I tried clone API by passing token but gives 401 error
@strogonoff hey Anton thanks for the answer, I'm trying to make pushes happen often, but I'm getting lots of
Failed to finalize commit "GitPushError: One or more branches were not updated: - refs/heads/master: failed to update ref" if send some concurrent requests...
so it's safe to say that multiple pushes on the same repository at the same time is impossible in isomorphic-git? I need to create some sort of lock
I believe locks are required. We use a lock to ensure our app doesn’t try to perform simultaneous operations on a repo. (Though this can’t prevent accessing the repo from outside the app.) @thelinuxlich
async-lock is one NPM package that can be used for that
the two that i have are:
git rev-parse HEAD:$(basename $(pwd)) andgit log --pretty=format:'%cI' -n 1 -- .
the first one gets the commit sha for the current directory
the second one gets the the commit date for the current directory
the second one gets the the commit date for the current directory
i'm thinking both could be solved if I could get the last commit for a specific directory
however, i couldn't seem to get https://isomorphic-git.org/docs/en/log.html to work for me with any combination of
dir and gitdir i tried
Since updating from 0.70.7 to 1.7.0 I'm keep getting the following error involving CacheFS, which causes certain operations to fail (e.g. cloning an existing repo):
errors.js:4 Uncaught (in promise) Error: ENOENT: [...whatever project path...]/.git/config
at CacheFS._lookup (CacheFS.js:115)
at CacheFS.stat (CacheFS.js:213)
at PromisifiedFS.stat (PromisifiedFS.js:290)
at PromisifiedFS.stat (PromisifiedFS.js:124)What do I need to do to resolve this?
hi,
I've submitted a new issue isomorphic-git/isomorphic-git#1231
basically I'm trying to pull & push changes and I encounter an error if a file (a.txt) was changed on the remote repo and other file (b.txt) was changed on the local repo
anyone encountered something like that?
I've submitted a new issue isomorphic-git/isomorphic-git#1231
basically I'm trying to pull & push changes and I encounter an error if a file (a.txt) was changed on the remote repo and other file (b.txt) was changed on the local repo
anyone encountered something like that?
Hey all , I am trying to test a locally deployed app against an in-house instance of GitLab. I stood up the @isomorphic-git/cors-proxy locally to get around the cross origin problems. However, as soon as a request is made to GitLab over https, I get the error: SELF_SIGNED_CERT_IN_CHAIN. I have set the http.sslVerfy to false in the browser, but it doesn't appear to affect the cors-proxy. What is the best way to work around this?
Anyone else getting 404 from GitLab when pulling from a repository? The URL seems a bit strange (but I don't have a lot of knowledge of GitLab internals). The GET sets git-upload-pack as a query parameter (this works without problems). When a POST is issued, the git-upload-pack is a path parameter. That's when I get a 404.
1 reply
@thelinuxlich Isomorphic-git don't support merge conflicts as the message say. I have no idea what you use mutexes for conflicts are not about write, I'm not sure if you know how git works but conflicts are when you want to merge two commits that modify same line (I think that if the line is in same chunk in same file)
I am getting this error in lighting-fs:
lightning-fs.js, line 1: TypeError: tSymbol.iterator.next is not a function
Anyhow, If I try to implement ssh will there be any problem?
Hey everyone
statusMatrix returns all files as [ 1, 2, 1]
im calling the code like this:
const matrix = await git.statusMatrix({ fs: this.fs, dir: 'D:/_dev/_repotest/branch' ) }).gitignore: 1 2 1
firstfile.md: 1 2 1
folder1/folder2/test2.md: 1 2 1
folder1/test.md: 1 1 1
new5.md: 1 2 1
nr4.md: 1 2 1
readme.md: 1 2 1
secondfile.md: 1 2 1
thiirdfile.md: 1 2 1what am i doing wrong? (using nodejs)
and there are no changes currently
1 reply
Everyone: I am so sorry it's been nearly a year(?!!!) since I've checked this chat. 😔 Mentally, the COVID-19 pandemic just completely pushed me beyond my limits and this was one of a couple facets of my life that got neglected.
I want to write a nice blog post explaining my dilemma, but in the meantime, just let it be known I really won't mind if the community (if there is one) forks the repo on order to continue the project. Maybe I can set up a proper "peaceful transition of power" for the actual
isomorphic-git GitHub org at some point, but honestly, I'd take advantage of the situation to rebrand with a less annoying name.