mirror of https://github.com/github/awesome-copilot.git synced 2026-03-17 14:45:13 +00:00

Files

suyask-msft 8bfc9f3c4b Source dataverse plugin externally from microsoft/Dataverse-skills (#1010 )

* Source dataverse plugin from microsoft/Dataverse-skills

The Dataverse plugin was previously bundled locally with a single
mcp-configure skill. It is now sourced externally from
microsoft/Dataverse-skills, which provides the full skill set:
init, setup, metadata, python-sdk, solution, mcp-configure, and overview.

- marketplace.json: update dataverse entry to external source format
- external.json: add Dataverse entry alongside Azure
- plugins/dataverse/: remove local plugin directory (now external)
- skills/mcp-configure/: remove top-level copy (now in external plugin)
- docs/README.plugins.md: update dataverse row with external link
- docs/README.skills.md: note mcp-configure moved to external plugin

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Make dataverse plugin docs generic to avoid stale counts

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Remove mcp-configure from skills index — now in external plugin

External plugins don't list their skills in README.skills.md
(consistent with azure-skills).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Revert manual edits to generated files

marketplace.json, README.plugins.md, and README.skills.md are
auto-generated. External plugins are discovered via external.json
and merged into marketplace.json by generate-marketplace.mjs.
Matches the Azure external plugin pattern — no manual doc entries.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Regenerate marketplace.json and docs after external plugin change

Run npm run build to pick up the new external dataverse entry and
remove the old local one from generated files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-17 08:32:26 +11:00

.gitkeep

Partners (#354 )

2025-10-29 06:07:13 +11:00

README.agents.md

Duplicate review (#1001 )

2026-03-16 10:27:54 +11:00

README.hooks.md

New hook: secrets-scanner (#1002 )

2026-03-16 11:05:35 +11:00

README.instructions.md

New GitHub Instruction: object orientated programming design patterns as GoF and SOLID (#1012 )

2026-03-16 10:43:53 +11:00

README.plugins.md

Source dataverse plugin externally from microsoft/Dataverse-skills (#1010 )

2026-03-17 08:32:26 +11:00

README.skills.md

Source dataverse plugin externally from microsoft/Dataverse-skills (#1010 )

2026-03-17 08:32:26 +11:00

README.workflows.md

Merge branch 'staged' into aw/relevance-check

2026-02-27 10:24:59 +11:00

README.workflows.md

⚡ Agentic Workflows

Agentic Workflows are AI-powered repository automations that run coding agents in GitHub Actions. Defined in markdown with natural language instructions, they enable event-triggered and scheduled automation with built-in guardrails and security-first design.

How to Contribute

See CONTRIBUTING.md for guidelines on how to contribute new workflows, improve existing ones, and share your use cases.

How to Use Agentic Workflows

What's Included:

Each workflow is a single .md file with YAML frontmatter and natural language instructions
Workflows are compiled to .lock.yml GitHub Actions files via gh aw compile
Workflows follow the GitHub Agentic Workflows specification

To Install:

Install the gh aw CLI extension: gh extension install github/gh-aw
Copy the workflow .md file to your repository's .github/workflows/ directory
Compile with gh aw compile to generate the .lock.yml file
Commit both the .md and .lock.yml files

To Activate/Use:

Workflows run automatically based on their configured triggers (schedules, events, slash commands)
Use gh aw run <workflow> to trigger a manual run
Monitor runs with gh aw status and gh aw logs

When to Use:

Automate issue triage and labeling
Generate daily status reports
Maintain documentation automatically
Run scheduled code quality checks
Respond to slash commands in issues and PRs
Orchestrate multi-step repository automation

Name	Description	Triggers
Daily Issues Report	Generates a daily summary of open issues and recent activity as a GitHub issue	schedule
OSPO Contributors Report	Monthly contributor activity metrics across an organization's repositories.	schedule, workflow_dispatch
OSPO Organization Health Report	Comprehensive weekly health report for a GitHub organization. Surfaces stale issues/PRs, merge time analysis, contributor leaderboards, and actionable items needing human attention.	schedule, workflow_dispatch
OSPO Stale Repository Report	Identifies inactive repositories in your organization and generates an archival recommendation report.	schedule, workflow_dispatch
OSS Release Compliance Checker	Analyzes a target repository against open source release requirements and posts a detailed compliance report as an issue comment.	issues, workflow_dispatch
Relevance Check	Slash command to evaluate whether an issue or pull request is still relevant to the project	slash_command, roles
Relevance Summary	Manually triggered workflow that summarizes all open issues and PRs with a /relevance-check response into a single issue	workflow_dispatch