Auto-generation of setup.py

[m-alisafaee]

Generate setup.py on merges to master that change poetry.lock or pyproject.toml.

Fixes #15

[rokroskar]

I believe this isn't going to work because of branch protection - the best you can do is push to a branch and automatically open a PR that could be automatically approved and merged. To do that, you need a token that is not the default token injected by github actions because those by design cannot trigger new actions.

[rokroskar]

You can look at this workflow in the main renku repo as an example.

[m-alisafaee]

I've created a token with under my account which will create PRs with my name. Do we have a RenkuBot token to use here?

[Panaetius]

Wouldn't it be better for the action to run on each branch and update the setup.py as a commit on that branch, if needed. Similar to how we create the Pipfile.lock in renku-python

[rokroskar]

Right, so run on the PR branch rather than master? That would certainly be easier

[m-alisafaee]

I thought of it in the beginning but I don't like to have a commit added to my PR/branches automatically.

[rokroskar]

I would remove the explicit ref (since it's a default) but if it needs to be there for some reason feel free to leave it in.