Skip to content

Commit 6a3a3d4

Browse files
authored
Merge pull request #1040 from rylev/remove-post-traige
Remove ability to use POST request for generating triage report
2 parents 3f19d77 + 0be604d commit 6a3a3d4

File tree

2 files changed

+2
-5
lines changed

2 files changed

+2
-5
lines changed

site/src/server.rs

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -448,9 +448,6 @@ async fn serve_req(server: Server, req: Request) -> Result<Response, ServerError
448448
.unwrap(),
449449
},
450450
),
451-
"/perf/triage" => Ok(to_triage_response(
452-
crate::comparison::handle_triage(check!(parse_body(&body)), &ctxt).await,
453-
)),
454451
_ => Ok(http::Response::builder()
455452
.header_typed(ContentType::html())
456453
.status(StatusCode::NOT_FOUND)

triage/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ and so it means the PR to include the triage details in TWiR can be merged short
1616
before publication. This time is also shortly before the weekly Rust compiler
1717
meeting, where the results are looked at.
1818

19-
## Generating the report
19+
## Generating the report
2020

2121
First, check the previous triage log entry. Look for responses in PRs, and
2222
follow up on any promised actions. (i.e. nag people!)
@@ -28,7 +28,7 @@ be the parent commit that we use for the current round of triage.
2828
Use the API endpoint to automate building the file:
2929

3030
```
31-
% curl https://perf.rust-lang.org/perf/triage -d "{\"start\": \"$PARENT\"}" > YYYY-MM-DD.md
31+
% curl "https://perf.rust-lang.org/perf/triage?start=$PARENT" > YYYY-MM-DD.md
3232
```
3333

3434
## Analysis

0 commit comments

Comments
 (0)