Skip to content
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

GitHub release tag propagated to artifacts from fork #80

Closed
wants to merge 4 commits into from

Conversation

mingness
Copy link
Collaborator

@mingness mingness commented Mar 24, 2025

  • edit build.gradle.kts to allow setting version from cli
  • get release tag from context, and process in input into gradle task as parameter
  • update documentation
  • remove unused TAG_NAME from release workflow

the version is set using a conditional, because one cannot set version from cli directly. This is just one way to solve this - if we move version to be set in a unified properties file, there might be yet another solution

@mingness mingness requested a review from Stefterv March 25, 2025 10:47
@mingness
Copy link
Collaborator Author

@Stefterv not sure why the PR review is not working - it seems to be a permission issue, but other runs of the workflow don't have this issue. so, I'll try to solve this, but in the meantime appreciate your thoughts on the work.

@mingness
Copy link
Collaborator Author

still not sure what the issue is, but it could be because I'm merging from a fork, and changing the workflow? Will create new PR from branch.

@mingness mingness closed this Mar 25, 2025
@mingness mingness changed the title GitHub release tag propagated to artifacts GitHub release tag propagated to artifacts from fork Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant