and leaving apart the status:published filtering, the issue data got parsed without breaking for the existing issue. A few notes, though:
The issues have two titles, one corresponding to the GitHub issue title, the other one in the body, corresponding to the field in the form. BHG 2020 had two as well. Might need to be considered at some point/later time if it happens to be misleading. The script only looks at the GitHub issue title.
For the sake of minimizing the effort, being consistent across year and not breaking things:
I would rename the Description field to Project Description in the issue form. If you think that is should not be, the regex should be changed in the script.
Same goes for the Link to the project field: the old template had Link to project repository/sources as title.
Otherwise, the names should be agreed upon once for good.
The issue template title has a default [Project]: text: if not deleted, it will appear in the title field. I would remove it; if not, all project sections on the website will have it.
The labeler is not working due to this line, and thus the issue is not getting labels, which is relevant for the website project data and brainmatch. Modifying the date to allow the labeler do its job, and assuming the label dictionary gets the appropriate changes (e.g. hashtags removed and regex refined maybe to avoid undesired hits), the script in PR #40 would get the labels without requiring changes.
The regexes may need to be adjusted to look for ### {field_name} to ensure that the field hit is the desired one: e.g.
(?<=### Description[^\v]{2})(.*)(?=[^\v]{2}###) would catch the data in the description (tested).
I ran the script in PR #40 on the repository here https://api.github.com/repos/Remi-Gau/global2021/
and leaving apart the
status:publishedfiltering, the issue data got parsed without breaking for the existing issue. A few notes, though:GitHubissue title, the other one in the body, corresponding to the field in the form. BHG 2020 had two as well. Might need to be considered at some point/later time if it happens to be misleading. The script only looks at theGitHubissue title.Descriptionfield toProject Descriptionin the issue form. If you think that is should not be, the regex should be changed in the script.Link to the projectfield: the old template hadLink to project repository/sourcesas title. Otherwise, the names should be agreed upon once for good.[Project]:text: if not deleted, it will appear in the title field. I would remove it; if not, all project sections on the website will have it.brainmatch. Modifying the date to allow the labeler do its job, and assuming the label dictionary gets the appropriate changes (e.g. hashtags removed and regex refined maybe to avoid undesired hits), the script in PR #40 would get the labels without requiring changes.The regexes may need to be adjusted to look for
### {field_name}to ensure that the field hit is the desired one: e.g.(?<=### Description[^\v]{2})(.*)(?=[^\v]{2}###)would catch the data in the description (tested).Originally posted by @jhlegarreta in https://github.com/brainhackorg/global2021/issues/32#issuecomment-932805057