This repository has been archived by the owner on Nov 2, 2023. It is now read-only.
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.
GitHub actions changes #21
GitHub actions changes #21
Changes from all commits
b6da5b9
1818995
47d89a5
e3d93c2
f4b4069
6854f40
91a0d48
83a886a
acb3ee1
f8c63fa
276895c
d2e33bb
aa1d7dd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is it worth ignoring
**.md
?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.
id prefer not to for now just in case. if it starts being annoying can change
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.
No cache? :(
I'd like it if we could figure out a better way of doing it than I have with Mobzy. I wonder if it'd be possible to get that working right in the NMS action itself. The only actual problem with the way I did it is it relies on NMS version being in gradle.properties and will update cache any time properties are updated.
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.
seeing as this change is focused on releasing, no
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.
Sounds good, but I'd like to look into that later. An issue would be nice, but what repo would that belong to? I think best to put it under the nms action itself, since we should probably add some info the the README on caching anyways.
This file was deleted.
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.
not just the shadow jar?
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.
Yes. My thinking was there is no harm in releasing both. The non shaded jar may be useful for explicitly adding a dependency when developing outside of gradle.
This file was deleted.