OpenConext / OpenConext/OpenConext-manage
Allow accepting/rejecting individual changes in a change request
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7
- Forks
- 13
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 7
Description
A change request can contain multiple changes. Currently, the entire change need to be rejected or accepted as a whole.
Instead, allow an admin to select which of the changes should be accepted, and which should be rejected. Automatically inform the requester of which changes were rejected.
(continued from #440)
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named in the issue. Start by tracing how change requests and their individual changes are represented, accepted, rejected, and communicated to requesters. Done means an admin can decide each change independently and the requester is informed about rejected changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100