Monorepo management for opam overlays
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Fix CLI help: remove tangled auth login, fix nonexistent push command

- Remove all references to 'tangled auth login' (no longer needed)
- Replace 'monopam push' references with 'monopam sync' workflow
- Update verse quick start to remove authentication step
- Replace AUTHENTICATION sections with HANDLES/HANDLE VALIDATION
- Document --skip-push and --skip-pull for finer control

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

+23 -29
+23 -29
bin/main.ml
··· 511 511 verse = \"verse\"\n\n\ 512 512 [identity]\n\ 513 513 handle = \"yourname.bsky.social\""; 514 - `S "AUTHENTICATION"; 515 - `P "Before running init, you must authenticate with the tangled network:"; 516 - `Pre "tangled auth login"; 514 + `S "HANDLE VALIDATION"; 517 515 `P 518 - "The handle you provide is validated against the AT Protocol identity \ 519 - system to ensure it exists and you are authenticated."; 516 + "The handle you provide identifies you in the opamverse community. \ 517 + It should be a valid domain name (e.g., yourname.bsky.social or \ 518 + your-domain.com)."; 520 519 `S "REGISTRY"; 521 520 `P 522 521 "The opamverse registry is a git repository containing an \ ··· 828 827 `S "QUICK START FOR NEW USERS"; 829 828 `P "Run these commands in order to get started:"; 830 829 `Pre 831 - "# Step 1: Authenticate with tangled (one-time setup)\n\ 832 - tangled auth login\n\n\ 833 - # Step 2: Create and initialize your workspace\n\ 830 + "# Step 1: Create and initialize your workspace\n\ 834 831 mkdir ~/tangled && cd ~/tangled\n\ 835 832 monopam verse init --handle yourname.bsky.social\n\n\ 836 - # Step 3: Sync all community members\n\ 833 + # Step 2: Sync all community members\n\ 837 834 monopam verse pull\n\n\ 838 - # Step 4: Browse their code\n\ 835 + # Step 3: Browse their code\n\ 839 836 ls verse/\n\ 840 837 cd verse/alice.bsky.social && dune build\n\n\ 841 - # Step 5: Keep everything updated (run daily/weekly)\n\ 838 + # Step 4: Keep everything updated (run daily/weekly)\n\ 842 839 monopam verse sync"; 843 840 `S "KEY CONCEPTS"; 844 841 `I ··· 874 871 `P "The expected sequence of commands for typical workflows:"; 875 872 `P "$(b,First-time setup) (once per machine):"; 876 873 `Pre 877 - "tangled auth login # authenticate\n\ 878 - monopam verse init --handle you.bsky.social # create workspace"; 874 + "monopam verse init --handle you.bsky.social # create workspace"; 879 875 `P "$(b,Syncing all members):"; 880 876 `Pre 881 877 "monopam verse pull # clone/pull all \ ··· 888 884 `P "$(b,Working in your own monorepo):"; 889 885 `Pre 890 886 "cd ~/tangled/mono\n\ 891 - monopam pull # fetch upstream \ 892 - changes\n\ 887 + monopam sync # sync with upstreams\n\ 893 888 # ... make edits ...\n\ 894 - monopam push # export to checkouts"; 889 + git add -A && git commit\n\ 890 + monopam sync --remote # push to upstreams"; 895 891 `S "INTEGRATION WITH MONOPAM"; 896 892 `P 897 893 "The verse system complements standard monopam commands. Your mono/ \ ··· 900 896 "# Work in your monorepo\n\ 901 897 cd ~/tangled/mono\n\ 902 898 monopam status\n\ 903 - monopam pull\n\ 899 + monopam sync # sync with upstreams\n\ 904 900 # ... make changes ...\n\ 905 - monopam push"; 901 + git add -A && git commit\n\ 902 + monopam sync --remote # push to upstreams"; 906 903 `P 907 904 "The verse/ directories are for reading and learning from others' \ 908 905 code. You generally don't push to them (unless you're a \ ··· 923 920 `I ("pull [<handle>]", "Clone/pull all members (or specific member)"); 924 921 `I ("sync", "Update registry and pull all members"); 925 922 `I ("fork <pkg> --from <handle> --url <url>", "Fork a package from a verse member"); 926 - `S "AUTHENTICATION"; 923 + `S "HANDLES"; 927 924 `P 928 - "Handle validation uses the AT Protocol identity system. The tangled \ 929 - CLI stores session credentials that monopam verse commands reuse."; 930 - `P "If you see 'Not authenticated', run:"; 931 - `Pre "tangled auth login"; 925 + "Handles identify community members. They are typically domain names \ 926 + like 'yourname.bsky.social' or 'your-domain.com'."; 932 927 ] 933 928 in 934 929 let info = Cmd.info "verse" ~doc ~man in ··· 1820 1815 `I 1821 1816 ( "4. monopam sync --remote", 1822 1817 "Sync again, including pushing to upstream git remotes" ); 1823 - `P "For finer control, use $(b,push) and $(b,pull) separately:"; 1818 + `P "For finer control over the sync phases:"; 1824 1819 `I 1825 - ( "monopam push", 1826 - "Export monorepo changes to checkouts (for manual review/push)" ); 1820 + ( "monopam sync --skip-pull", 1821 + "Export monorepo changes to checkouts only (skip fetching remotes)" ); 1827 1822 `I 1828 - ( "monopam pull", 1829 - "Pull remote changes into monorepo (when you know there are no local \ 1830 - changes)" ); 1823 + ( "monopam sync --skip-push", 1824 + "Pull remote changes only (skip exporting local changes)" ); 1831 1825 `S "CHECKING STATUS"; 1832 1826 `P "Run $(b,monopam status) to see the state of all repositories:"; 1833 1827 `I ("local:+N", "Your monorepo is N commits ahead of the checkout");