|
| 1 | +# ============================================================================== |
| 2 | +# Jira Integration Environment Variables |
| 3 | +# ============================================================================== |
| 4 | +# Copy this file to .env and fill in your actual values |
| 5 | +# |
| 6 | +# Required for Jira API access |
| 7 | +JIRA_BASE_URL=https://coursedog.atlassian.net |
| 8 | +JIRA_EMAIL=your-email@domain.com |
| 9 | +JIRA_API_TOKEN=your-jira-api-token |
| 10 | + |
| 11 | +# Optional: Jira project key for filtering (leave empty to search all projects) |
| 12 | +JIRA_PROJECT_KEY= |
| 13 | + |
| 14 | +# ============================================================================== |
| 15 | +# GitHub Context Variables (for local testing) |
| 16 | +# ============================================================================== |
| 17 | +# These are automatically set when running in GitHub Actions |
| 18 | +# For local testing, set them manually to simulate different scenarios |
| 19 | + |
| 20 | +# Git reference (branch or tag) |
| 21 | +# Examples: refs/heads/main, refs/heads/staging, refs/heads/dev |
| 22 | +GITHUB_REF=refs/heads/staging |
| 23 | + |
| 24 | +# Event type that triggered the workflow |
| 25 | +# Options: push, pull_request, pull_request_target |
| 26 | +GITHUB_EVENT_NAME=push |
| 27 | + |
| 28 | +# Path to the GitHub event payload file |
| 29 | +# For local testing, use ./update_jira/event.local.json |
| 30 | +GITHUB_EVENT_PATH=./update_jira/event.local.json |
| 31 | + |
| 32 | +# Repository in owner/repo format |
| 33 | +GITHUB_REPOSITORY=coursedog/notion-scripts |
| 34 | + |
| 35 | +# GitHub token for API access (required for fetching commit data) |
| 36 | +GITHUB_TOKEN=your-github-token |
| 37 | + |
| 38 | +# ============================================================================== |
| 39 | +# Testing Variables |
| 40 | +# ============================================================================== |
| 41 | +# For running verification and test scripts |
| 42 | + |
| 43 | +# Test issue key for custom field verification |
| 44 | +TEST_JIRA_ISSUE_KEY=DEX-36 |
| 45 | + |
| 46 | +# Enable dry-run mode (will log actions but not actually update Jira) |
| 47 | +# DRY_RUN=true |
| 48 | + |
| 49 | +# ============================================================================== |
| 50 | +# Custom Field Configuration Reference |
| 51 | +# ============================================================================== |
| 52 | +# The following custom fields are used for deployment tracking (from ALL-593): |
| 53 | +# |
| 54 | +# customfield_11473: Release Environment (select field) |
| 55 | +# - Option ID 11942: staging |
| 56 | +# - Option ID 11943: production |
| 57 | +# |
| 58 | +# customfield_11474: Stage Release Timestamp (datetime) |
| 59 | +# - Set automatically on staging deployments |
| 60 | +# |
| 61 | +# customfield_11475: Production Release Timestamp (datetime) |
| 62 | +# - Set automatically on production deployments |
| 63 | +# |
| 64 | +# To verify these field IDs are correct for your Jira instance: |
| 65 | +# node utils/verify-custom-fields.js |
| 66 | +# |
| 67 | +# To test updating these fields: |
| 68 | +# node utils/test-custom-field-update.js DEX-36 |
0 commit comments