Because knotmirror is listening to creation of sh.tangled.repo
records, the actual git repository should exist on sh.tangled.repo
creation event.
Signed-off-by: Seongmin Lee git@boltless.me
Because knotmirror is listening to creation of sh.tangled.repo
records, the actual git repository should exist on sh.tangled.repo
creation event.
Signed-off-by: Seongmin Lee git@boltless.me
name field to repo.create
oauth.User type
oauth.MultiAccountUser
MultiAccountUser.Active from template
.Handle from oauth.AccountInfo
AuthReturnInfo
AddAccount session data
oauth.ClientSessionData
TANGLED_PDS_USER_DOMAIN for user handle check
Because knotmirror is listening to creation of `sh.tangled.repo`
records, the actual git repository should exist on `sh.tangled.repo`
creation event.
Signed-off-by: Seongmin Lee <git@boltless.me>
Ah, right, so that was why we were creating PDS records first. I will bring @oyster.cafe's work to support that.
makes sense, in which case, we can abandon this PR and live with the slight delay for now!
Because knotmirror is listening to creation of `sh.tangled.repo`
records, the actual git repository should exist on `sh.tangled.repo`
creation event.
Signed-off-by: Seongmin Lee <git@boltless.me>
you you explain the transaction rollback steps here? if the record creation fails will the knot have the directory created inside it?