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

A reviewer must provide a reason when rejecting a push 💬 #605

Open
JamieSlome opened this issue Jun 13, 2024 · 1 comment
Open

A reviewer must provide a reason when rejecting a push 💬 #605

JamieSlome opened this issue Jun 13, 2024 · 1 comment
Assignees
Labels
dashboard Part of CISO/OSPO experience to access UI good first issue Good for newcomers hacktoberfest

Comments

@JamieSlome
Copy link
Member

Is your feature request related to a problem? Please describe.

Screenshot 2024-06-13 at 11 13 43

When a reviewer rejects a push, either through the UI or API, it is unclear why the push has been rejected. This makes it difficult for the developer to understand what changes need to be made and requires further friction to resolve the issue.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Enforce a custom text input for a rejection reason when rejecting a push. As we look to automate GitProxy further, this will also come in handy when we auto-reject pushes as we will need a description and information about why a push was auto-rejected.

@JamieSlome JamieSlome added good first issue Good for newcomers dashboard Part of CISO/OSPO experience to access UI labels Jun 13, 2024
@divinetettey
Copy link
Contributor

Hi @JamieSlome I would love to pick this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard Part of CISO/OSPO experience to access UI good first issue Good for newcomers hacktoberfest
Projects
None yet
Development

No branches or pull requests

2 participants