Should commit replace directive if it's pointing to a local module?

As far as I understand, replace directive is useful to test published 3rd party packages. What if I'm using it to point to a local module just so Go is aware of its location, is it safe to commit it to the repo? What are the pitfalls in doing so? I'm using v1.18.x.

UPDATE

Here's how my project looks

app/
|---lambdaFuncOne/
|   |---go.mod
|---lambdaFuncTwo/
|   |---go.mod
|---pkg/
|   |---customOne/
|   |   |---go.mod
|---go.work

pkg/customOne is used in both lambdaFuncOne and lambdaFuncTwo, so their go.mod file has this

replace github.com/user/proj/app/pkg/customOne => ../pkg/customOne

It's a relative path so I guess it's always valid?

go.work has this

go 1.18

use (
   ./lambdaFuncOne
   ./lambdaFuncTwo
   ./pkg/customOne 
)

In brief you can commit the replace as long as you also commit the things it is redirecting to. We often do this to work on a package locally before pushing to github. You might also use it if you have modified an open source package but don't want to share the changes.

Originally, a common use for replace was for temporarily testing or trying an alternative version of a package. But many people were accidentally committing go.mod with the temporary replace clause so that is why Go 1.18 introduced the workspace file.

So use workspace for local temporary experiments. Use replace for (semi)permanent redirection. Always commit your go.mod file but never commit the workspace file.

This is my understanding. I'm sure someone will correct me if I'm wrong.