Use the remote git feature of cargo.toml and reference a commit hash of your fork.

Reply to this note

Please Login to reply.

Discussion

That's what I'm doing now. Issue is I have SQL migrations that are project specific and I don't want to pollute my fork. Might just move it to it's own crate.

Migrations could be it's own folder in the repo you created. Then use relative paths for reference? Sounds like it's pretty specific