-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release repository argument #975
Conversation
Don't maintain the return values by hand and instead use auto.
GitHub always uses the owner/name combination for defining the repository. Therefore add a function that converts this repository into a owner name (space project) tuple.
GitHub always uses the owner/name combination for identifying a repository. Therefore we should allow passing this as input for creating and signing releases.
Conventional Commits Report
🚀 Conventional commits found. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest to replace space
with owner
, so it is aligned everywhere ... now it's mixed up ...
Of course we can do that. Personally I would love to get rid of space/owner and project completely and replaces all with repository. But this should go into another PR. |
I thought you will leave it for compatibility reasons ... |
Maybe we just drop it after the actions and workflow are adjusted. |
What
Allow to pass
--repository
instead of--space
and--project
topontos-release
create
andsign
.Why
GitHub nearly always passes an "owner/name" combination for identifying the repository. Therefore we should support this pattern too. For example this is the only way to get the repo in an action from
${{ github.repository }}
via the github contextChecklist