Providing a PDF in the repo just makes the Git history balloon, since it's a binary file and Git can't track changes very well. Thus, it would be a lot better to provide the raw LaTeX source and just leave it up to the user to compile the PDF. Worst case scenario, they can just load everything into Overleaf and compile it there, but it doesn't use much beyond fairly standard packages and should be relatively easy. Obviously, the PDF can be removed from the repo after that.
Providing a PDF in the repo just makes the Git history balloon, since it's a binary file and Git can't track changes very well. Thus, it would be a lot better to provide the raw LaTeX source and just leave it up to the user to compile the PDF. Worst case scenario, they can just load everything into Overleaf and compile it there, but it doesn't use much beyond fairly standard packages and should be relatively easy. Obviously, the PDF can be removed from the repo after that.