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
Not sure if I should add here (please let me know if I should create a different issue), but Roboquat is also not moving columns for the following tickets:
Removing from platform inbox, because in terms of priorities we need to focus on SOC2 for now.
Furthermore, there are unclear technical challenges:
how to map PRs to Gitpod-versions, because commit-sh1 change on pr-merge.
how to deal with PRs that are not local to a meta-deployment, ide-deployment or workspace-deployment? Those PRs are practically in a "half deployed" state.
Furthermore, there are unclear technical challenges:
how to map PRs to Gitpod-versions, because commit-sh1 change on pr-merge.
Prow has 2 important concepts for jobs. presubmits and postsubmits which act on pull requests and merges, respectively. I believe we need a postsubmit job that can do all the "after merge work" such as:
Bug description
When gitpod-io/gitpod#6048 was opened, @roboquat requested reviews in gitpod-io/gitpod#6048 (comment) and labels were updated in the corresponding issue in gitpod-io/gitpod#5050 (comment), however, the issue was not moved to the review column in groundwork[1], see gitpod-io/gitpod#5050 (comment).
Steps to reproduce
Have not tried reproducing this but approving the PR before @roboquat runs could be the root cause of this issue, see gitpod-io/gitpod#6048 (comment).
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: