isomorphic-git GitHub org at some point, but honestly, I'd take advantage of the situation to rebrand with a less annoying name.
Hi all,
first off ty for this library, it's made some really interesting ideas possible for me in the last couple years.
I put together an ostensibly working version of fetch using protocol v2 based on the WIP that existed https://github.com/isomorphic-git/isomorphic-git/compare/main...whytheplatypus:feat/v2-fetch .. should I clean this up and open a PR?
hey @jcubic - like rhedin, I'm building an entirely client side (i.e. "serverless") app. I'm looking into the feasibility of making isomorphic-git work peer-to-peer over webrtc without any server based repository as a way to sync shared content. in my scenario there'd be worst case a few dozens of users on a given repository.
assuming i have the webrtc wiring taken care of, do you see any challenges in making isopmorphic-git work p2p? presumably i somehow want to wire "fetch" with the webrtc peer connection, with some kind of lighterweight protocol sitting on top to indicate that other clients need to sync with a repo where changes were just made
await fs.promises.writeFile(
`/${imageFolder}/${file.name}`,
new Uint8Array(buffer)
);
let status = await this.git.statusMatrix({
fs,
dir: `/${imageFolder}`,
});
console.log(status);
await this.git.add({
fs,
dir: `/${imageFolder}`,
filepath: file.name,
});
await this.git.commit({
fs,
dir: '/',
author: this.author,
message: `Updated the '${serializer.title}' header image`,
});
