feat(workflows): add community ops automation workflow example #32
Loading…
Reference in New Issue
No description provided.
Delete Branch "puygob236/gitlink-cli:community-ops-automation-pr"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This PR adds a reproducible end-to-end workflow example under
examples/workflows/community-ops-automation/.The example operationalizes existing
gitlink-clicapabilities for a community operations scenario. It collects repository, issue, pull request, and release activity, normalizes the returned data, generates a weekly Markdown report, drafts Release Notes, emits a structured JSON summary, and can optionally publish the summary back to a GitLink issue comment.What is included
scripts/gitlink_workflow.py: workflow runner for data collection, metric aggregation, report generation, and optional issue publishing.scripts/run_demo.ps1: one-command reproduction script for Windows/PowerShell environments.examples/sample_config.jsonandexamples/demo_active_config.json: reproducible repository configurations.examples/demo_outputs/: checked-in sample outputs generated from real GitLink repositories.docs/: architecture, quickstart, runbook, verification record, and operational notes.tests/test_gitlink_workflow.py: unit tests for data normalization, report generation, stale item detection, and issue comment command construction.Validation
python -m unittest discover -s testsRan 5 tests ... OKThe workflow has also been validated against real GitLink repositories, including
GitLink/gitlink-cliandpuygob236/gitlink-cli, with generated reports and example outputs included in the workflow directory.