Improve release.yml

[paxcema]

Right now this file is helpful to trigger releases into PyPI when they come from a branch other than stable or staging, which is very useful for updating old versions without messing up those two branches.

However, when the release comes from those two branches, I'm fairly certain a duplicate PyPI release job is triggered, by sequentially running lightwood.yml first, then release.yml.

We should modify one of them so that this duplicate procedure is avoided.

[ddninja]

Hi @paxcema , I would like to work on this.
I will suggest to remove the PyPI release job from lightwood.yml

[paxcema]

Hi @ddninja, sure.

How about merging release.yml logic into lightwood.yml so that all deployment-related jobs are here?

We only want to avoid duplicate runs, the problem with your approach above is that we do want to deploy in PyPI when pushing to stable.

[ddninja]

@paxcema If we merge release.yml logic into lightwood.yml, the test job will also be executed if the release is published.
If this is expected behaviour then I will do that, also once we merge these file , release.yml will not be needed any more.
Or do you want to run test job only if build is pushed to stable/staging branch.

[ddninja]

@paxcema i have raised a pull request. can you please check.

[paxcema]

Closed via #1196, thanks @ddninja!