You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wow very cool analysis! I was inspired by this idea and created something similar that uses the same read method, but to write, it uses a machine account that sends an issue (with data) to the repo. This triggers a github action, which takes the issue data and writes it back to the json file. Even if multiple users attempt to write at the same time, you can make the github action retry committing to the repo if it fails (which will happen if two actions try to write at the same time). This effectively solves the problem of concurrent conflicts (to an extent, because if there are enough write requests at the same time then the action will stop retrying, and the data will be lost). However, it is much slower than just committing, and isn't that useful when trying to use github as a fast database. Anyway, I think this idea is very cool, and you can see my repo here and my implementation here. I also believe that you can make github actions merge and delete branches, instead of doing it manually, so that would make the process more automated.
Thanks! :)
The text was updated successfully, but these errors were encountered:
Wow very cool analysis! I was inspired by this idea and created something similar that uses the same read method, but to write, it uses a machine account that sends an issue (with data) to the repo. This triggers a github action, which takes the issue data and writes it back to the json file. Even if multiple users attempt to write at the same time, you can make the github action retry committing to the repo if it fails (which will happen if two actions try to write at the same time). This effectively solves the problem of concurrent conflicts (to an extent, because if there are enough write requests at the same time then the action will stop retrying, and the data will be lost). However, it is much slower than just committing, and isn't that useful when trying to use github as a fast database. Anyway, I think this idea is very cool, and you can see my repo here and my implementation here. I also believe that you can make github actions merge and delete branches, instead of doing it manually, so that would make the process more automated.
Thanks! :)
The text was updated successfully, but these errors were encountered: