Skip to content

chore: Update governance.yml to remove repo-name input#47

Merged
damaz91 merged 1 commit into
mainfrom
chore/clean-governance
Jun 26, 2026
Merged

chore: Update governance.yml to remove repo-name input#47
damaz91 merged 1 commit into
mainfrom
chore/clean-governance

Conversation

@damaz91

@damaz91 damaz91 commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Description

Removed the repo-name input from the governance workflow. The central governance script will start inferring the repo name implicitly in Universal-Commerce-Protocol/.github#31

Category (Required)

Please select one or more categories that apply to this change.

  • Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
  • Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
  • Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
  • Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
  • Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
  • Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
  • SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
  • Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
  • UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
  • Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Checklist

  • I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
  • I have updated the documentation (if applicable).
  • My changes pass all local linting and formatting checks.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • (For Core/Capability) I have included/updated the relevant JSON schemas.
  • I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

Removed the repo-name input from the governance workflow.
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@damaz91 damaz91 marked this pull request as ready for review June 26, 2026 12:08
@damaz91 damaz91 merged commit 6f9141c into main Jun 26, 2026
10 of 12 checks passed
@damaz91 damaz91 deleted the chore/clean-governance branch June 26, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants