-
Notifications
You must be signed in to change notification settings - Fork 60
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
Post Stakwork Run ID to Front End on Sucessful Send #2119
Comments
Join and post in this Sphinx Tribe for assignments: sphinx.chat://?action=tribeV2&pubkey=0306abbf1523b90303a0b65ca3d4e1359f5079348dc4ee33625d030613875b9f47&host=tribes.v2.sphinx.chat No Github requests / tags will be monitored. |
@humansinstitute please assign me? |
@humansinstitute can i help? |
@humansinstitute I can help please assign |
@saithsab877 can we update this please. "message": "${project_id}", This will be easier to render on the front end. |
@humansinstitute Sure |
Ticket Name: Implement WebSocket Update for Stakwork Run ID Submission
Task
ticket.go
to process the response from the Stakwork API.project_id
.project_id
.sendMessage
function fromwebsocket/pool.go
to broadcast this message.Outcome
This will allow display of a link to the current run to be displayed in the ticket editor component.
Design
https://github.com/stakwork/sphinx-tribes/blob/master/handlers/ticket.go#L376C2-L432C3
Code Snippet
WebSocket Message
We already send a response that we have sent the message here: https://github.com/stakwork/sphinx-tribes/blob/master/handlers/ticket.go#L410C3-L420C6
Please update the message sent to:
Acceptance Criteria
ticket.go
to process and unmarshal the Stakwork response.project_id
from the Stakwork response.project_id
.sendMessage
fromwebsocket/pool.go
to send the WebSocket message.The text was updated successfully, but these errors were encountered: