nim-works/nimskull

Improve UX for /merge command

Open

#972 opened on Oct 18, 2023

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Nim (39 forks)auto 404
cienhancementgood first issue

Repository metrics

Stars
 (346 stars)
PR merge metrics
 (PR metrics pending)

Description

Right now not a lot is shown on whether a command succeed or failed. Having a response (ie. done by pushing a comment or appending to the requester's comment) would help handling the "why is it not working?" issue a lot better

Contributor guide

Research direction
Examine the current implementation of the /merge command in the bot code and identify where to add a comment or response to indicate success or failure.
Tech stack
None
Domain
clitooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNim
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70