Open jamesbraza opened 1 month ago
Hmm this is virgin soil here. :) I have never used such a setup, so I have to guess a bit, but I would say: cd in to those packages and add a suffix, yes. Please let me know how it goes, so we can add something to the docs.
I have something like this:
- name: Check albatross build
uses: hynek/build-and-inspect-python-package@v2
with:
upload-name-suffix: -albatross
- name: Check bird-feeder build
uses: hynek/build-and-inspect-python-package@v2
with:
path: packages/bird-feeder
upload-name-suffix: -bird-feeder
- name: Check seeds build
uses: hynek/build-and-inspect-python-package@v2
with:
path: packages/seeds
upload-name-suffix: -seeds
And it leads to this summary:
We should put the upload-name-suffix
into the summary title, so everything doesn't say Package Contents
, it can say Package-albatross Contents
(and be distinguishable)
I have something like this workspace layout, which leads to this GitHub Action:
Looking at version
2.9.0
's inputs: https://github.com/hynek/build-and-inspect-python-package/blob/v2.9.0/action.yml#L9-L25Is the correct way to handle this to invoke
build-and-inspect-python-package
three times, with a differentupload-name-suffix
each time?