Skip to content

After renaming the organization, update the repository remote. #63

@Will-thom

Description

@Will-thom

Proceed with the following changes to keep the roadmap documented.

Repository migration:

Current:
github.com/pr-maven/pr-maven-cli

Target:
github.com/pr-cli/pr-maven-cli

GitHub will automatically redirect requests from the old repository URL to the new one. However, the old organization name may become available for others to claim, so all controlled references should be updated.

After renaming the organization, update the repository remote.

SSH.
HTTPS.

Post-migration checklist:

  • Update README references
  • Update GitHub Actions badges
  • Update docs/installation.md
  • Review and update links in important issues and pull requests
  • Update GitHub Actions workflows
  • Update hardcoded URLs in scripts
  • Update package/module metadata, if applicable
  • Update website or custom domain references, if applicable

Long-term organization strategy:

The organization will become the umbrella for a family of deterministic PR context CLIs, each focused on a single package manager and its ecosystem.

Examples:

  • pr-maven-cli
  • pr-npm-cli
  • pr-gradle-cli
  • pr-pnpm-cli

Guiding principle:

Start narrow. One package manager, one failure model, one deterministic contract.

Deterministic means the output does not depend on LLMs, loose heuristics, random ordering, network access, or subjective interpretation. It is based on parsing and rules.

Metadata

Metadata

Assignees

Labels

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions