Release: Close related milestone

[danirabbit]

It would be super convenient if we could also close the related milestone (if it exists).

For example, we release "1.0.0", then we close the milestone named "1.0.0"

[cassidyjames]

@danrabbit what happens to open issues/PRs on the associated milestone when it's closed?

[danirabbit]

If you mean "what currently happens": they stay open and assigned to that milestone

If you mean "what ideally happens": they should be assigned to a new milestone or at least removed from that milestone

[dawidd6]

I guess it could be done like this:

1. Read JSON object file from $GITHUB_EVENT_PATH and get milestone.number (check if it exists first)
2. curl --method PATCH --data "$DATA" https://api.github.com/repos/$GITHUB_REPOSITORY/milestones/$MILESTONE_NUMBER?access_token=$GITHUB_TOKEN with $DATA:

DATA="
{
  \"title\": \"$VERSION\",
  \"state\": \"closed\"
}
"

Note, that this is untested.