sourceallies / sourceallies/hacker-rank-queue

After accepting a review, send a second message instead of replacing contents of the message they accepted

Open
#559 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5
Forks
0
Avg merge
3d 3h
Merged PRs (30d)
5

Description

Some teammates are confused about where the links to do a review are at after they accept (we used to get an Email).

My hunch is that teammates aren't realizing the message contents are being replaced with everything they need. It might be more visible if we sent a separate message to them instead of replacing the contents of the message.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing the review-accept flow and the Slack message update logic; confirm where the accepted review message is replaced. Done means the original message remains available and a separate message clearly provides the links needed to complete the review.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.