feat: updated code/refactored added hackmd integration

Author: ovflowd

.env.example

@@ -1,15 +1,14 @@
-# GitHub Authentication
-GITHUB_TOKEN=your_github_personal_access_token_here
+# Required: GitHub Token (Needs "repo" permissions)
+# GITHUB_TOKEN=your_personal_access_token_or_org_token
 
-# Google APIs Authentication
-# You can get these from the Google Cloud Console
-GOOGLE_CLIENT_ID=your_google_client_id_here
-GOOGLE_CLIENT_SECRET=your_google_client_secret_here
-GOOGLE_REDIRECT_URI=http://localhost:3000/oauth2callback
+# Required: HackMD Configuration
+# HACKMD_API_TOKEN=your_hackmd_api_token
+# HACKMD_TEAM_NAME=your_hackmd_team_name_optional # Defaults to your own personal space
 
-# Optional: Google Service Account (for GitHub Actions)
-# GOOGLE_SERVICE_ACCOUNT_EMAIL=your_service_account_email_here
-# GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY=your_service_account_private_key_here
+# Google Calendar API Authentication
+# You can get this from the Google Cloud Console
+# Create an API Key and restrict it to the Google Calendar API
+# GOOGLE_API_KEY=your_google_calendar_api_key_here
 
 # Optional: Directory paths (defaults to current directory and home)
 # MEETINGS_CONFIG_DIR=./

.github/workflows/create-meeting-artifacts.yml

@@ -40,10 +40,10 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@1e60f620b9541d16bece96c5465dc8ee9832be0b # v4.0.3
         with:
           node-version-file: '.nvmrc'
           cache: 'npm'
@@ -54,17 +54,18 @@ jobs:
       - name: Create meeting artifacts
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          GOOGLE_SERVICE_ACCOUNT_EMAIL: ${{ secrets.GOOGLE_SERVICE_ACCOUNT_EMAIL }}
-          GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY: ${{ secrets.GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY }}
+          HACKMD_API_TOKEN: ${{ secrets.HACKMD_API_TOKEN }}
+          HACKMD_TEAM_NAME: ${{ secrets.HACKMD_TEAM_NAME }}
+          GOOGLE_API_KEY: ${{ secrets.GOOGLE_API_KEY }}
         run: node create-node-meeting-artifacts.mjs ${{ github.event.inputs.meeting_group }}
 
       - name: Upload artifacts
         if: always()
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@50769540e7f4bd5e21e526ee35c689e35e0d6874 # v4.4.0
         with:
           name: meeting-artifacts-${{ github.event.inputs.meeting_group || 'tsc' }}
           path: |
             ~/.make-node-meeting/
-            minutes_temp.txt
+            *.md
           retention-days: 7
           if-no-files-found: ignore

.github/workflows/test.yml

@@ -0,0 +1,39 @@
+name: Test Suite
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [22.x, 'latest']
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@1e60f620b9541d16bece96c5465dc8ee9832be0b # v4.0.3
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run linting
+        run: npm run lint
+
+      - name: Run tests
+        run: npm test
+
+      - name: Check format
+        run: npm run format:check

.gitignore

@@ -1,3 +1,15 @@
+# Node.js Packages
 node_modules/
-client_secret.json
-package-lock.json
+
+# Environment File
+.env
+
+# Test artifacts and temporary files
+test/fixtures/temp/
+test/snapshots/*.snap
+*.log
+coverage/
+
+# Files created during unit test runs
+*.sh
+meeting-test/

.prettierignore

@@ -0,0 +1 @@
+templates/

AUTHORS

@@ -1 +1,2 @@
 Michael Dawson <mdawson@devrus.com>
+Claudio Wunder <cwunder@gnome.org>

README.md

@@ -1,13 +1,14 @@
 # Node.js Meeting Artifacts Creator
 
-A modern Node.js application that creates GitHub issues and Google Docs for Node.js team meetings. This tool automates the process of reading meeting configuration, fetching calendar events, creating meeting minutes documents, and posting GitHub issues.
+A modern Node.js application that creates GitHub issues and HackMD documents for Node.js team meetings. This tool automates the process of reading meeting configuration, fetching calendar events, creating meeting minutes documents, and posting GitHub issues.
 
 ## 📋 Requirements
 
 - Node.js 22+ (LTS)
 - GitHub Personal Access Token
-- Google Cloud Project with Calendar and Drive APIs enabled
-- OAuth credentials or Service Account credentials
+- Google Cloud Project with Calendar API enabled (for meeting scheduling)
+- Google API Key for Calendar access
+- HackMD API Token (for meeting minutes)
 
 ## 🔑 Authentication Setup
 
@@ -18,23 +19,25 @@ A modern Node.js application that creates GitHub issues and Google Docs for Node
    - `repo` (Full control of private repositories)
    - `user` (Read user information)
 
-### Google Authentication
+### HackMD Authentication
 
-#### Option 1: OAuth (for local development)
+1. Go to [HackMD](https://hackmd.io/) and sign in to your account
+2. Navigate to Account Settings > API Tokens
+3. Create a new API token for the meeting artifacts tool
+4. Optionally, create or join a team workspace for better organization
 
-1. Go to [Google Cloud Console](https://console.cloud.google.com/)
-2. Create a new project or select an existing one
-3. Enable the Google Calendar API and Google Drive API
-4. Create OAuth 2.0 credentials (Desktop Application)
-5. Add credentials to `.env` file
+### Google Authentication (Calendar Only)
 
-#### Option 2: Service Account (for GitHub Actions)
+#### API Key Authentication (Recommended)
 
 1. Go to [Google Cloud Console](https://console.cloud.google.com/)
 2. Create a new project or select an existing one
-3. Enable the Google Calendar API and Google Drive API
-4. Create a Service Account and generate JSON key file
-5. Add credentials to environment variables
+3. Enable the Google Calendar API
+4. Go to **Credentials** → **Create Credentials** → **API Key**
+5. Restrict the API key to the Google Calendar API for security
+6. Add the API key to your environment variables as `GOOGLE_API_KEY`
+
+**Note:** API Keys provide simplified authentication and are sufficient for read-only calendar access. They don't require complex OAuth flows or service account setup.
 
 ## 🎯 Available Meeting Commands
 
@@ -195,8 +198,8 @@ node --env-file=.env create-node-meeting-artifacts.mjs tsc
 The application creates:
 
 1. **GitHub Issue**: Posted to the configured repository with meeting details and agenda
-2. **Google Doc**: Meeting minutes document stored in the `/nodejs-meetings` folder
-3. **Console Output**: Links to both the created issue and document
+2. **HackMD Document**: Meeting minutes document in Markdown format with collaborative editing
+3. **Console Output**: Links to both the created issue and HackMD document
 
 ## 🔧 Configuration
 
@@ -205,19 +208,15 @@ The application creates:
 #### Required
 
 - `GITHUB_TOKEN`: GitHub Personal Access Token
+- `HACKMD_API_TOKEN`: HackMD API token for creating and managing documents
 
-#### Google Authentication (choose one)
-
-**OAuth (Local Development):**
+#### HackMD Configuration (optional)
 
-- `GOOGLE_CLIENT_ID`: OAuth client ID
-- `GOOGLE_CLIENT_SECRET`: OAuth client secret
-- `GOOGLE_REDIRECT_URI`: OAuth redirect URI (default: `http://localhost:3000/oauth2callback`)
+- `HACKMD_TEAM_NAME`: HackMD team name/path for team workspaces
 
-**Service Account (GitHub Actions):**
+#### Google Authentication
 
-- `GOOGLE_SERVICE_ACCOUNT_EMAIL`: Service account email
-- `GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY`: Service account private key (JSON format)
+- `GOOGLE_API_KEY`: Google Calendar API Key for read-only calendar access
 
 #### Optional
 

TEMPLATES_DOCUMENTATION.md

@@ -1,6 +1,8 @@
 This document contains empty versions of each template needed to successfully create meeting artifacts for a Committee, Working Group, Initiative, or Team. These documents need to go in the [/templates](./templates) directory in this repository.
 
-There are only four variables in the documents that _need_ to be changed:
+## Template Variables
+
+There are several variables in the documents that need to be configured:
 
 - **`<name>`:** The name of the Committee, Working Group, Initiative, or Team that meeting artifacts are being created for.
 - **`<shortname>`:** The abbreviated or shortened name for a group, used in each filename to connect associated files together.
@@ -11,6 +13,22 @@ There are only four variables in the documents that _need_ to be changed:
 - **`<issue-label>`:** an optional label for the created issue itself.
 - **`<observer>`:** Name of an observer in a group's meetings.
 
+## Meeting Properties Reference
+
+The following properties are available in meeting base templates and can be used in meeting issue generation:
+
+- **`CALENDAR_FILTER`:** The name of calendar events that mark the group's meeting date/time
+- **`CALENDAR_ID`:** The Google Calendar ID for the Node.js calendar (typically `nodejs.org_nr77ama8p7d7f9ajrpnu506c98@group.calendar.google.com`)
+- **`USER`:** The GitHub username/organization (typically `nodejs`)
+- **`REPO`:** The repository name where meeting issues are created
+- **`GROUP_NAME`:** The full name of the Committee, Working Group, Initiative, or Team
+- **`AGENDA_TAG`:** The label used to search for agenda items in GitHub issues and PRs
+- **`HOST`:** Meeting host information
+- **`JOINING_INSTRUCTIONS`:** Instructions for joining the meeting (Zoom links, YouTube streams, etc.)
+- **`ISSUE_LABEL`:** Optional label to apply to the created meeting issue
+
+These properties are defined in the `meeting_base_<shortname>` template files and are substituted when generating meeting issues.
+
 # Invited
 
 The [GitHub Team](https://help.github.com/articles/about-teams/) to invite. The @mention should be a GitHub Team whose members are all invidiuals who are always invited.