One good solution is to symlink the repo to the Blender's addon location, then develop using your favorite editor
2 other solutions I came across that are great to use:
if you package your blender addon as a python package (create a pyproject.toml), then you can do an editable install with pip to a site packages folder. this creates a .pth file, which is similar to a symlink. some kind of pointer to a folder. now every time you restart the code refreshes.
disadvantage is every time you update the version in the toml you need to reinstall with pip.
there is also a blender extension for vs code, which is a bit of a faff to setup. but once done, it creates a live link between blender and vscode. any update in vs code instantly shows in blender. dont even need to reload module or restart blender.
i used to use symlink, but the disadvantage is if you swap branch it might try delete the folder. affecting your source files. the other solutions don't have this issue.
hi i see you recommend symlink.
2 other solutions I came across that are great to use:
pyproject.toml), then you can do an editable install with pip to a site packages folder. this creates a.pthfile, which is similar to a symlink. some kind of pointer to a folder. now every time you restart the code refreshes. disadvantage is every time you update the version in the toml you need to reinstall with pip.i used to use symlink, but the disadvantage is if you swap branch it might try delete the folder. affecting your source files. the other solutions don't have this issue.