Standard Git structure and update workflow for simple unregistered packages

Nathan_Boyer
Tue, 11 May 2021 18:26:49 +0000
New to Julia

I have a package hosted on Github that I work on in VSCode (both of which I am new to). It currently has master, feature-x, and bugfix-x branches that I created as well as some branches from CompatHelper. All branches get merged into master once they are finished.

However, I noticed a workflow issue when trying to update my package dependencies. How can I test new versions of my package dependencies with my package before adding them to the compat list in the master Project.toml? The Project.toml has to be updated before ] update will work, but then my package says it is compatible with dependent packages before I know if that is true.

I imagine I need to add a new intermediate dev branch to my Git structure, but I don’t know how to change CompatHelper so it points to a different branch. Also, complicating my Git tree sounds like a bad idea. I already almost always screw up my merges and end up manually copy and pasting into a new commit for master instead.

4 posts - 2 participants