Skip to main content

Synopsis

create-node-meeting-artifacts.mjs <group> [options]
The <group> argument is required. It identifies the meeting group whose templates are used to generate the issue, minutes document, and calendar lookup.

Arguments

group
string
required
The meeting group shortname (e.g., tsc, build, uvwasi). Must match a set of four template files in the templates/ directory:
  • invited_<group>
  • observers_<group>
  • meeting_base_<group>
  • minutes_base_<group>
See Supported Meeting Groups for the full list of available shortnames.

Options

--dry-run
boolean
default:"false"
Show output without creating or updating anything. The tool still reads configuration, fetches agenda issues from GitHub, and generates content — but it prints the result to the console instead of writing to HackMD or GitHub. Calendar fetching is also skipped.
--force
boolean
default:"false"
Create a new GitHub issue and a new HackMD document even if one already exists with the same title. By default the tool searches for an existing open issue and updates it if found.
--verbose
boolean
default:"false"
Show debug output. Passes console as the Octokit logger, which causes console.debug output to appear for every GitHub API call.

Usage examples

node create-node-meeting-artifacts.mjs tsc

Exit codes

CodeMeaning
0Success — artifacts were created, or no meeting was found for the current week (both are normal outcomes).
Non-zeroError — a required configuration value is missing, a template file cannot be read, or an API call fails.
The tool uses commander v14 for argument parsing. The --env-file flag is a Node.js built-in available since Node.js 20.6.0 and is not part of this package.

Build docs developers (and LLMs) love