Skip to content

API: /evals/batch #9

Description

@joeoneil

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

APIAPI Route issuebackendBackend specific issue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions