Hey @xuanxu! So I've been fumbling around with the code and configurations, and we are at the point where the bot (@scoobies) responds to hello and help on this ticket here: scipy-conference/scipy_proceedings_test#1. Currently, any response that is specified as "editor only" is failing with an authorization error:

2021-03-16T00:18:59.449788+00:00 app[web.1]: 2021-03-16 00:18:59 - Octokit::Unauthorized - GET https://api.github.com/orgs/scipy-conference/teams?per_page=100: 401 - Requires authentication // See: https://docs.github.com/rest/reference/teams#list-teams:

Possibly this is due to a misspecification of the teams? I don't know where one can find the GitHub ID, so I used the name of the team here:

config files:

• 2023 Code of Conduct
• 2023 Editors

PaperFile class:

• find papers ending in .tex or .rst

@scoobies check references currently searches for a file ending in .bib near the .rst or .tex paper file. This works when there's only one file, but if there are other .rst or .tex files, say in sub-directories, then it fails to find the .bib file:

Checking the BibTeX entries failed with the following error:

Couldn't find bibliography entry

This fork has not pull from upstream in a while and there are several new features and fixes available since then.
One of them would fix the error incorrectly labeling DOIs as invalid happening here.

Pulling main should be straightforward, after that depending on the number of possible conflicts I'm not sure if the better strategy would be to merge main into the scipy branch or rebase scipy on top of main.

When we construct the endpoints in procbuild, we use the github user name and branch name combination from the PR label to construct a unique ID per paper. In buffy, we're currently using the login of the person who opens the PR, but this is not necessarily the same as the login of the person (or organization) who owns the branch getting merged in.

An example of this not working as expected is here: scipy-conference/scipy_proceedings#639 (comment)

We can pull the login of the repo owner from the API response via head -> repo -> owner -> login, but it may be simpler to grab head -> label and replace the colon with a dash.