Stream: helpdesk (published)

Topic: ✔ dev local package from another package fails github act...

Brynjar Smári Bjarnason (Nov 30 2022 at 10:29):

Hey.
I have created a package ABC that is on Github and it runs Github actions for building and testing the code and everything works.

I have another package XYZ that I am developing which requires me to make changes to ABC as well. In XYZ i did a dev ~/projects/ABC which brought the local package to my XYZ and changes to ABC show up in XYZ.

Now I have committed the changes to ABC and pushed to Github, it builds and passes the tests on Github actions.

When I commit and push XYZ it refers to my local ABC and Github actions fail.

Should I add the ABC package in some other way to XYZ?

Rik Huijzer (Nov 30 2022 at 11:13):

Are you committing the Manifest.toml for XYZ as well? Without it, the package should use the registered version from the registry. If you plan to publish the package, it is generally advised to not commit the Manifest.toml

What you also can do to fix it is to explicitly install the ABC package in XYZ via something like

steps:
    [...]
    - julia --project -e 'using Pkg; Pkg.add(; url="https://github.com/<username>/ABC.jl")'
    - julia-actions/julia-runtest@v1

Brynjar Smári Bjarnason (Nov 30 2022 at 11:23):

Thanks!
I am committing the Manifest. I'll look into removing that.
Aha so you install ABC in the Github action before installing the rest of the packages? That would work!

Fredrik Ekre (Nov 30 2022 at 11:39):

You can add ABC by URL instead of tracking the local path.

Brynjar Smári Bjarnason (Dec 01 2022 at 07:32):

Fredrik Ekre said:

You can add ABC by URL instead of tracking the local path.

Well then i can't develop XYZ without pushing ABC to GitHub. I want local changes to be available in XYZ while developing.

@Rik Huijzer solution works! Thanks a lot.

Notification Bot (Dec 01 2022 at 07:33):

Brynjar Smári Bjarnason has marked this topic as resolved.

Last updated: Dec 28 2024 at 04:38 UTC