exp

.github/workflows/assign-milestones.js

@@ -1,14 +1,10 @@
-// get the project
+// assign a milestone to issues or PRs added to a project, with a name corresponding
-// check if the name matches a version x.y or x.y.z
+// to the name of the project - create the milestone if it does not exist
-// created
+//
-//   check that there is a corresponding milestone
+// adding a *second* project to the issue will update the milestone accordingly
-//   else create that milestone
+// removing that project will reset the milestone entirely (not use the other project)
-//   and assign the issue to the milestone
+// and, no idea what happens if one very quickly adds and removes an issue
-// deleted
+//
-//   get the issue
-//   if issue is not closed,
-//   remove issue from milestone, if any
-
 // an issue or PR actually becomes a card (or, a card is actually created...) when
 // it's move to a project column for the first time - being assigned to the project
 // and showing in project's backlog is not enough.

.github/workflows/publish-release.yml

@@ -1,6 +1,6 @@
 name: Publish Release
 on:
-  workflow_dispatch
+  workflow_dispatch:
     inputs:
       description: 'Version'
       required: true