-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] Lang Agenda — Proposed FCPs: include concerns and FCP notes #1596
[feature] Lang Agenda — Proposed FCPs: include concerns and FCP notes #1596
Conversation
@rustbot claim |
r? @nikomatsakis @Mark-Simulacrum Concerned about a couple things:
|
src/github.rs
Outdated
let initiating_comment_html_url = | ||
format!("{}#issuecomment-{}", issue.html_url, fk_initiating_comment,); | ||
let init_comment = issue | ||
.get_comment(&client, fk_initiating_comment.try_into()?) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should I just make IssueDecorators.fpc_details.fk_initiating_comment
a usize
from the get-go?
- [**Tracking Comment**]({{issue.fcp_details.bot_tracking_comment_html_url}}): {{issue.fcp_details.bot_tracking_comment_content}} | ||
- [**Initiating Comment**]({{issue.fcp_details.initiating_comment_html_url}}): {{issue.fcp_details.initiating_comment_content}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wondering what happens if issue.fcp_details
is passed in as None
That's not great. That said, I typically run this script once per week... ...still, I wonder if there's a way to combine this into a single graphql query or something. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, seems kind of like I expected! Left some nits and questions.
src/github.rs
Outdated
); | ||
let bot_tracking_comment_content = quote_reply(&fcp.status_comment.body); | ||
let fk_initiating_comment = fcp.fcp.fk_initiating_comment; | ||
let initiating_comment_html_url = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably orthogonal, but I'm surprised we don't use some library for this sort of thing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you referring to accessing the comment link or to the quote_reply
function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unrelated but I'm similarly surprised we're using a home-baked parser rather than a command line library (like clap) to take in commands — surely wouldn't be too hard to treat a github comment like command line input
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant something like https://crates.io/crates/octocrab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is kind of interesting, especially b/c octocrab is in here, but nothing in src/github.rs
seems to use it
Lines 250 to 255 in 2a37c45
pub struct Context { | |
pub github: GithubClient, | |
pub db: crate::db::ClientPool, | |
pub username: String, | |
pub octocrab: Octocrab, | |
} |
@chazkiker2 Can you say if this seems ready to go on your end? My feeling is that we should probably go ahead and merge presuming it mostly works, and then if there's bugs to be fixed or rate limiting etc we can either revert or fix those depending on complexity. |
@Mark-Simulacrum shoot — sorry, kinda lost track of this. If you think the |
Yeah, it seems a little messy, but since we don't have obvious next steps we can probably merge. With #1599 there might be simplification possible but seems also a little difficult to put a finger on. I'll merge this tomorrow to let some of the changes I merged today go live first, I think. |
@Mark-Simulacrum okay sounds like a decent plan :). sorry for the slowness! |
@Mark-Simulacrum btw i don’t think i have merge access on this repo, so feel free to merge in whenever you’re ready |
Description
See an example of the new lang agenda (with updated FCP details) in this HackMD