palandlom
palandlom
In my case - it wasn't solved. My suggestion - consider to use https://neo4j.com/docs/cypher-manual/current/constraints/ in addition to neosemantic OR/AND implement restrictions on a "higher" level of application.
No - just workaround - make "force pull" by original git command after failed `pull`: ```bash git reset --hard origin/branch-name ``` ```golang // UpdateRepositoryByUrl performs git pull for all repositories...
> ```go > Reset(&git.ResetOptions{ > Mode: git.HardReset, > }) > ``` It is needed to reset to branch of remote repo i.e. `git reset --hard origin/branch` not just `git reset...
The [spec](https://github.com/jaydenseric/graphql-multipart-request-spec) expects that there should be `operations`, `map` and file fields - e.g.: ```curl curl localhost:3001/graphql \ -F operations='{ "query": "mutation($files: [Upload!]!) { multipleUpload(files: $files) { id } }",...