Fix NuGet publish #48
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
mmm I thought GITHUB_REF_NAME was supposed to work as well so I didn't say anything before but I use that here: /~https://github.com/PhantomGamers/SUWSF/blob/main/.github/workflows/publish.yaml#L19 |
Windows10CE
force-pushed
the
fix-nuget-publish
branch
from
5515fe5 to
230cd0c
Compare
Windows10CE
force-pushed
the
fix-nuget-publish
branch
from
230cd0c to
4377f58
Compare
|
Actually fixed now, GitHub Actions uses the action files from the actual release tag, not from master, so it took me a bit longer than I would like to admit to figure out that |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GITHUB_REF_NAME environment variable didn't have the tag as expected, so this switches to using the same action to get the tag as the release workflow