ComputerScienceHouse / ComputerScienceHouse/conditional-backend
API: /evals/batch
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Batch view / definition routes
**7 Routes**
---
**POST** /evals/batch
_accessible to all upperclassmen_
Creates a new batch with either specified criteria or specific members
If created by the evals director, should be automatically approved.
---
**GET** /evals/batch
_accessible to all members_
Gets all currently approved batches
If evals, also shows pending batches
---
**PUT** /evals/batch/{id}
_accessible to evals director_
Modifies an existing batch, either approving a member-submitted batch or manually altering an approved batch
---
**POST** /evals/batch/pull/{user}
_accessible to evals director_
Pulls a user from all batches, and marking them as being pulled, so they cannot be placed into any new batches manually or automatically.
---
**POST** /evals/batch/pr
_accessible to all upperclassmen_
Submits a request to pull a user from all batches, must include a reason.
---
**GET** /evals/batch/pr
_accessible to evals director_
Shows all pending and approved pull requests
Discuss: Should members be able to view their own submitted PRs and their status (pending / denied / approved)?
---
**PUT** /evals/batch/pr
_accessible to evals director_
Modifies a pull request, marking as approved / denied.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.