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
{{ message }}
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
Right now the probot client's workflow for bisect is
start bisect
wait for bisect to finish
give the results in a new comment
Instead, it should be:
add a comment saying that the bisect is beginning
start bisect
wait for bisect to finish
give the results by updating the comment created in step 1
The bot should be refactored in a way s.t. it should not care whether the first comment exists yet or not, e.g. GithubClient.setBugbotComment(markdown: string) (or whatever function name) so that the comment is created if it doesn't exist, or updated if it does exist.
We will need this functionality for the matrix as well, but adding it for the existing bisect feature means it could be developed now before the matrix code is ready.
The text was updated successfully, but these errors were encountered:
Right now the probot client's workflow for bisect is
Instead, it should be:
The bot should be refactored in a way s.t. it should not care whether the first comment exists yet or not, e.g.
GithubClient.setBugbotComment(markdown: string)
(or whatever function name) so that the comment is created if it doesn't exist, or updated if it does exist.We will need this functionality for the matrix as well, but adding it for the existing bisect feature means it could be developed now before the matrix code is ready.
The text was updated successfully, but these errors were encountered: