-
Notifications
You must be signed in to change notification settings - Fork 42
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
Release WG meeting issues are not being created #147
Comments
@richard, the tool depends on the name in the calendar matching what is in the templates so its worth double checking that. The google APIs also seem a bit "flaky" sometimes in terms of matching. If you can give me a few days notice in advance of a meeting for a meeting when the issue has not been generated I can see if just running the tooling generates the meeting or not and if not do some debugging. |
@mhdawson FYI the next Release WG meeting is next week, Thursday 8th February 2023. It's probably too early for the issue to normally be generated, but I'll mention it now as you're away next week. |
@richardlau did you check that the templates and entry in the calendar match? Unfortunately for me to easily debug it needs to be between the Monday the issue would be generated and the meeting itself and I will be away before the next one. |
|
Looks like nodejs/Release#980 was created successfully this time for the next meeting. I'll close. |
Reopening -- although nodejs/Release#980 was created it was not populated with any of the labelled agenda items. |
All I can think of at this point it some rate limiting by github. Split up the creation on mondays into two different jobs that run an hour appart to see if that helps. |
nodejs/Release#983 looks okay. |
For the last two Release WG meetings (11 Jan 2024 and 14 Dec 2023[1]) the expected issues in https://github.com/nodejs/Release have not been created. It looks like meeting issues are still being created for the other working groups/teams so it would be good to understand/resolve why the process isn't working for the Release WG.
[1] Note nodejs/Release#971 exists but I had to ask @mhdawson to generate it.
The text was updated successfully, but these errors were encountered: