Have you searched for this feature request?
Problem Statement
To test the code of idpbuilder, when not yet released or part of a PR, it is needed to clone the project, checkout the branch/PR and build it. This is not an issue for the developers as they have installed go and needed tools on their machine but this is not the case, when you want to test it part of a github workflow or equivalent.
This is why I propose that part of a PR merged on main, we generate the idpbuilder binaries + compressed files and publish them on the github project repository to let a user to get them
Possible Solution
Example: https://trstringer.com/github-actions-create-release-upload-artifacts/
Alternatives Considered
N/A
Have you searched for this feature request?
Problem Statement
To test the code of idpbuilder, when not yet released or part of a PR, it is needed to clone the project, checkout the branch/PR and build it. This is not an issue for the developers as they have installed go and needed tools on their machine but this is not the case, when you want to test it part of a github workflow or equivalent.
This is why I propose that part of a PR merged on main, we generate the idpbuilder binaries + compressed files and publish them on the github project repository to let a user to get them
Possible Solution
Example: https://trstringer.com/github-actions-create-release-upload-artifacts/
Alternatives Considered
N/A