{"owner":"huggingface","repo":"speech-to-speech","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Repository Instructions\n\n- Never include `codex` in branch names or pull request titles.\n- Never merge a pull request into `main` unless the user explicitly asks the agent to perform the merge and then confirms when asked immediately before the merge. Requests to review, fix, prepare, finish, or get a pull request ready do not count as merge authorization. Once the pull request is ready, report its status and ask for confirmation; merge only after a clear follow-up confirmation.\n- For existing/open pull requests, do not amend, squash, rebase-rewrite, or force-push follow-up changes. Make new commits and push normally unless explicitly asked to rewrite history.\n- Keep release pull requests focused on version metadata and release documentation.\n- Do not commit local build artifacts such as `dist/`, `build/`, or generated wheel/sdist files.\n\n## Publishing to PyPI\n\nPyPI publishing is handled by GitHub Actions in `.github/workflows/publish.yml`. The workflow runs on pushed tags that match `v*`, builds the package with `uv build`, checks the artifacts with `twine check --strict`, and publishes through the configured `pypi` environment.\n\nTo prepare a release:\n\n1. Confirm the intended version is not already published on PyPI.\n2. Bump `version` in `pyproject.toml`.\n3. Bump `__version__` in `src/speech_to_speech/__init__.py`.\n4. Open and merge a pull request with only the release preparation changes.\n\nTo publish after the release PR is merged:\n\n1. Update `main` locally: `git checkout main && git pull origin main`.\n2. Create an annotated tag for the version: `git tag -a vX.Y.Z -m \"Release vX.Y.Z\"`.\n3. Push the tag: `git push origin vX.Y.Z`.\n4. Watch the `Publish` GitHub Actions workflow complete successfully.\n5. Verify the new version appears at `https://pypi.org/project/speech-to-speech/`.\n\nOnly upload manually if the GitHub Actions workflow is unavailable and the maintainers have explicitly chosen that fallback.\n"},"files":{"AGENTS.md":"# Repository Instructions\n\n- Never include `codex` in branch names or pull request titles.\n- Never merge a pull request into `main` unless the user explicitly asks the agent to perform the merge and then confirms when asked immediately before the merge. Requests to review, fix, prepare, finish, or get a pull request ready do not count as merge authorization. Once the pull request is ready, report its status and ask for confirmation; merge only after a clear follow-up confirmation.\n- For existing/open pull requests, do not amend, squash, rebase-rewrite, or force-push follow-up changes. Make new commits and push normally unless explicitly asked to rewrite history.\n- Keep release pull requests focused on version metadata and release documentation.\n- Do not commit local build artifacts such as `dist/`, `build/`, or generated wheel/sdist files.\n\n## Publishing to PyPI\n\nPyPI publishing is handled by GitHub Actions in `.github/workflows/publish.yml`. The workflow runs on pushed tags that match `v*`, builds the package with `uv build`, checks the artifacts with `twine check --strict`, and publishes through the configured `pypi` environment.\n\nTo prepare a release:\n\n1. Confirm the intended version is not already published on PyPI.\n2. Bump `version` in `pyproject.toml`.\n3. Bump `__version__` in `src/speech_to_speech/__init__.py`.\n4. Open and merge a pull request with only the release preparation changes.\n\nTo publish after the release PR is merged:\n\n1. Update `main` locally: `git checkout main && git pull origin main`.\n2. Create an annotated tag for the version: `git tag -a vX.Y.Z -m \"Release vX.Y.Z\"`.\n3. Push the tag: `git push origin vX.Y.Z`.\n4. Watch the `Publish` GitHub Actions workflow complete successfully.\n5. Verify the new version appears at `https://pypi.org/project/speech-to-speech/`.\n\nOnly upload manually if the GitHub Actions workflow is unavailable and the maintainers have explicitly chosen that fallback.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Repository Instructions\n\n- Never include `codex` in branch names or pull request titles.\n- Never merge a pull request into `main` unless the user explicitly asks the agent to perform the merge and then confirms when asked immediately before the merge. Requests to review, fix, prepare, finish, or get a pull request ready do not count as merge authorization. Once the pull request is ready, report its status and ask for confirmation; merge only after a clear follow-up confirmation.\n- For existing/open pull requests, do not amend, squash, rebase-rewrite, or force-push follow-up changes. Make new commits and push normally unless explicitly asked to rewrite history.\n- Keep release pull requests focused on version metadata and release documentation.\n- Do not commit local build artifacts such as `dist/`, `build/`, or generated wheel/sdist files.\n\n## Publishing to PyPI\n\nPyPI publishing is handled by GitHub Actions in `.github/workflows/publish.yml`. The workflow runs on pushed tags that match `v*`, builds the package with `uv build`, checks the artifacts with `twine check --strict`, and publishes through the configured `pypi` environment.\n\nTo prepare a release:\n\n1. Confirm the intended version is not already published on PyPI.\n2. Bump `version` in `pyproject.toml`.\n3. Bump `__version__` in `src/speech_to_speech/__init__.py`.\n4. Open and merge a pull request with only the release preparation changes.\n\nTo publish after the release PR is merged:\n\n1. Update `main` locally: `git checkout main && git pull origin main`.\n2. Create an annotated tag for the version: `git tag -a vX.Y.Z -m \"Release vX.Y.Z\"`.\n3. Push the tag: `git push origin vX.Y.Z`.\n4. Watch the `Publish` GitHub Actions workflow complete successfully.\n5. Verify the new version appears at `https://pypi.org/project/speech-to-speech/`.\n\nOnly upload manually if the GitHub Actions workflow is unavailable and the maintainers have explicitly chosen that fallback.\n","category":"root","tokens":485}]}