-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(oracle): github issue/pr verificaiton logic #8
Conversation
0xpatrickdev
commented
Nov 16, 2023
•
edited
Loading
edited


- wire up front end Claim form (wip)
20c04f9
to
fc53f36
Compare
typo: verificaiton |
assignees (first:1) { | ||
nodes { | ||
resourcePath | ||
name | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why no url
for assignees
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
resourcePath is /${username}
, so this was easier to parse
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we use id
. There may be a way to get it via a relation but didn't did too hard
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm. if we use url
for both PR author and issue assignee, there's no need to parse anything, right?
onSuccess: (data) => { | ||
// Handle success | ||
console.log("success", data); | ||
toast.success("Bounty claimed successfully!"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo: listen for invitation, build tx, and prompt user to sign keplr tx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm kicking the tires; it seems to work pretty well.
For example, I tried to claim based on one of your PRs, and I got:
{"level":30,"time":1700175686110,"pid":2988393,"hostname":"bldbox","reqId":"req-3","req":{"method":"POST","url":"/job/claim","hostname":"localhost:5000","remoteAddress":"127.0.0.1","remotePort":54794},"msg":"incoming request"}
{"level":30,"time":1700175686725,"pid":2988393,"hostname":"bldbox","reqId":"req-3","res":{"statusCode":403},"responseTime":614.2947220206261,"msg":"request completed"}