Skip to content
Assign Milestone on Close

Fix beta build by better clearly distinguishing between the main nvda launcher and the l10nutil exe files #353

Sign in to view logs

Fix beta build by better clearly distinguishing between the main nvda launcher and the l10nutil exe files

Fix beta build by better clearly distinguishing between the main nvda launcher and the l10nutil exe files #353

Workflow file for this run

.github/workflows/assign-milestone-on-close.yml at 14816df
name: Assign Milestone on Close
env:
MILESTONE_ID: ${{ vars.MILESTONE_ID }}
on:
issues:
types: [closed]
pull_request_target:
types: [closed]
permissions:
issues: write
pull-requests: write
jobs:
assign-milestone:
runs-on: ubuntu-latest
steps:
- name: Check if milestone is set
id: check-milestone
uses: actions/github-script@v7
with:
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
const issueOrPr = context.payload.issue || context.payload.pull_request;
if (!issueOrPr.milestone) {
core.setOutput('milestoneNotSet', 'true');
} else {
core.setOutput('milestoneNotSet', 'false');
}
- name: Assign default milestone
if: steps.check-milestone.outputs.milestoneNotSet == 'true'
uses: actions/github-script@v7
with:
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
const issueOrPrNumber = (context.payload.issue || context.payload.pull_request).number;
const repository = context.repo;
await github.rest.issues.update({
...repository,
issue_number: issueOrPrNumber,
milestone: process.env.MILESTONE_ID
});