Skip to content
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

The prompt information of rerere needs to be optimized. #640

Open
1 task done
Mini256 opened this issue Jul 12, 2021 · 2 comments
Open
1 task done

The prompt information of rerere needs to be optimized. #640

Mini256 opened this issue Jul 12, 2021 · 2 comments
Labels
lifecycle/rotten type/bug The issue is confirmed as a bug.

Comments

@Mini256
Copy link
Member

Mini256 commented Jul 12, 2021

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

What is expected?

We need more friendly prompt information to let developers know the running status of rerere:

  1. 'Waiting previous PRs merged' can be prompted on the CI status during the rerere wait PR merge
  2. .rerere.json file needs to be formatted
  3. The message body of retesting commit should be refined

What is actually happening?

At present, the prompt information of rere is somewhat difficult to view.

image

@Mini256 Mini256 added the type/bug The issue is confirmed as a bug. label Jul 12, 2021
@ti-chi-bot
Copy link
Member

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle stale

@ti-chi-bot
Copy link
Member

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle rotten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants