-
Notifications
You must be signed in to change notification settings - Fork 29
gha/release: Improve workflow input descriptions and ordering #307
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,35 +8,35 @@ on: | |
| workflow_dispatch: | ||
| inputs: | ||
| ref: | ||
| description: 'Ref (e.g. v0.10.0)' | ||
| description: 'Tag/ref to build (e.g. v0.10.0)' | ||
| required: true | ||
| type: string | ||
| repo: | ||
| description: 'Override default repo' | ||
| required: false | ||
| type: string | ||
| release: | ||
| description: 'Release type' | ||
| description: '(optional) Release type to create in https://github.com/docker/packaging/releases' | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Perhaps a multi-line text block to also outline what the different options do; - `pushonly` pushes the artifacts as an image, but does not create a (draft) release.
- `draft` pushes the artifacts as an image, and creates a draft release in https://github.com/docker/packaging/releases
- ...
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| required: false | ||
| default: 'pushonly' | ||
| default: 'draft' | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. With a better description, do we perhaps want the default to be be kept And .... maybe make that a
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It was fine when testing, but now 99% cases you actually trigger it is for the actual deploy. You can always delete the draft afterwards, but you can't easily regenerate the release if you do it as |
||
| type: choice | ||
| options: | ||
| - pushonly | ||
| - draft | ||
| - prerelease | ||
| - release | ||
| distros: | ||
| description: 'Distros to build (comma-separated, e.g. "debian12,ubuntu2204")' | ||
| description: '(optional, empty = all supported) Distros to build (comma-separated, e.g. "debian12,ubuntu2204")' | ||
| required: false | ||
| type: string | ||
| default: '' | ||
|
Comment on lines
+25
to
28
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wondering how long the list is, and if we could have / generate a checkbox-list for this 🤔
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should get rid of it after this one is merged: https://github.com/docker/release-repo/pull/727 |
||
| revision: | ||
| description: | | ||
| Revision of the package to build. Only in case we ever would have to re-build an already published release with a packaging-only change. | ||
| (optional) Revision of the package to build. Only in case we ever would have to re-build an already published release with a packaging-only change. | ||
| Default for a tagged/upstream release is 1. | ||
| required: false | ||
| type: string | ||
| default: '' | ||
| repo: | ||
| description: '(optional) Override default repo (if want to build from a different Github repo/fork)' | ||
| required: false | ||
| type: string | ||
|
|
||
| jobs: | ||
| release: | ||
|
|
||

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.
Can we provide a valid non-tag example? I think this would also accept;
refs/xx/xx/(we could have a PR ref as example)git describeformat likely as well (e.g.api/v1.52.0-beta.3-36-g5680867af8)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 wouldn't encourage non-tag usage right now, as the VERSION string is derived from the reference.
So until we have an option to override the visible version (see #260) I wouldn't want to provide other examples than tags.