NASA-AMMOS / NASA-AMMOS/plandev-ui
Include more info for understanding the source and context of a merge request
Open
Nobody has claimed this yet.
clipper
feature
- Dominant language
- Svelte
- Stars
- 42
- Forks
- 14
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 10
Description
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
No response
Describe the feature request
Merge Requests modal missing:
- Time/date of request (an important differentiating identifier in addition to requestor/owner)
- Whether request is incoming or outcoming
- Space for commenting
Time/date and comments should also be included in Merge Review UI:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Merge Requests modal and Merge Review UI entry points in the client application, then compare their current content with the requested context. Done means both views show the request time/date, indicate whether it is incoming or outgoing, and provide space for comments; the issue also links related comment work in issue #221.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100