Skip to content

fix: remove replace directive from go.mod - #33

Merged
fb929 merged 1 commit into
anyproto:mainfrom
cboct:main
Nov 27, 2025
Merged

fb929 merged 1 commit into
anyproto:mainfrom
cboct:main

Conversation

@cboct

@cboct cboct commented Nov 27, 2025

Copy link
Copy Markdown
Contributor

  • I understand that contributing to this repository will require me to agree with the CLA

Description

This PR fixes go.mod by removing a replace directive that prevents go install to work as described in the tools' READMEs.

What type of PR is this? (check all applicable)

  • 🍕 Feature
  • 🐛 Bug Fix
  • 📝 Documentation Update
  • 🎨 Style
  • 🧑‍💻 Code Refactor
  • 🔥 Performance Improvements
  • ✅ Test
  • 🤖 Build
  • 🔁 CI

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

  • 👍 yes
  • 🙅 no, because they aren't needed
  • 🙋 no, because I need help

Added to documentation?

  • 📜 README.md
  • 📓 tech-docs
  • 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

The developer who uses the replace directive in go.mod will want to switch to Go workspaces to get the same behavior as with the replace directive:

go work init .
go work use ../any-sync

This will create a go.work file in the current project, linking to the local clone of any-sync project.
(BTW, go.work files don't need to, and should not, be added to the repo.)

@github-actions

github-actions Bot commented Nov 27, 2025 •

Copy link
Copy Markdown

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@cboct

cboct commented Nov 27, 2025

Copy link
Copy Markdown
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@fb929
fb929 merged commit 4aecbc5 into anyproto:main Nov 27, 2025
1 of 2 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants