manaflow-ai / manaflow-ai/cloudrouter

Confirm public contribution policy and licensing

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
5
Forks
2
PR merge metrics
No merged PRs in 30d

Description

This public non-fork repository has 25 commits and its README says MIT, but it has no LICENSE file, CONTRIBUTING.md, SECURITY.md, CI workflow, or branch protection. The README says the CLI source lives in https://github.com/manaflow-ai/manaflow/tree/main/packages/cloudrouter, which may make this repository a documentation or skill mirror rather than the canonical source.\n\nPlease confirm whether this repository accepts external pull requests. If it does, add the canonical license file, contributor and security guidance, CI, and branch protection, then decide whether CLA Assistant v3 is legally required. If it does not, document the canonical source and mark this repository as a read-only mirror.\n\nNo CLA workflow is proposed until this ownership and legal decision is recorded.

Please name at least two maintainers who will review security and CLA changes.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the README and the referenced packages/cloudrouter path to confirm whether this repository is canonical or a mirror. Then resolve the external-contribution policy with maintainers before changing repository governance. Done means the ownership decision, review maintainers, legal CLA decision, and either the requested guidance and controls or read-only mirror status are recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, github-actions
Domain
ci-cd, devops, documentation, security
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.