Skip to content

docs: prep mkdocs edit_uri for copybara_push -> main rename (#119)#139

Open
igopalakrishna wants to merge 2 commits intogoogle:copybara_pushfrom
igopalakrishna:chore/prepare-main-rename
Open

docs: prep mkdocs edit_uri for copybara_push -> main rename (#119)#139
igopalakrishna wants to merge 2 commits intogoogle:copybara_pushfrom
igopalakrishna:chore/prepare-main-rename

Conversation

@igopalakrishna
Copy link
Contributor

Fixes #119

It's a good idea to open an issue first for discussion.

This PR is a small prep step for renaming the default branch from copybara_push to main (Issue #119).
Since copybara_push is likely tied to Copybara sync, the internal destination ref may need updating after the rename.

What changed

  • mkdocs.yml: Added notes to keep edit_uri pointing at copybara_push for now, and to update it to main after the branch rename (avoids breaking “Edit this page” links before main exists).

Maintainer follow-ups (after merge)

  • Rename branch in GitHub: copybara_push -> main

  • Update mkdocs.yml edit_uri to edit/main/docs/

  • Verify Copybara config/sync doesn’t hardcode copybara_push

  • Tests pass (CI will confirm)

  • Appropriate changes to documentation are included in the PR

- Update mkdocs.yml edit_uri from copybara_push to main
- GitHub Actions workflow already supports both branches
- This PR prepares the codebase; actual rename must be done by maintainers

Related to issue google#119
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.

Renaming the Main Branch

1 participant