Collective update from fake template #32
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
razor-x
force-pushed
the
updates-from-template-3
branch
from
8d76c72
to
0e378ee
Compare
razor-x
force-pushed
the
updates-from-template-3
branch
from
0e378ee
to
f1ee849
Compare
razor-x
force-pushed
the
updates-from-template-3
branch
from
09a6d3f
to
82af96d
Compare
|
Bundle |
seveibar
approved these changes
Jul 20, 2023
|
@seveibar Ah yea, as in breaking changes? It might be but we are pre v1. Actually I've been meaning to make this update for quite a while now as my plan was to do this update before v1. |
|
@razor-x yep sounds good! |
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.
Nothing here is new. These updates are ported from our core fake template. Fixes a few known issues and update the structure to match the current standard.
Still worth some more eyes, as while I did my best diff-fu to bring things up to date, it's possible there is a mistake (already found and fixed some when I reviewed it here), plus it's a good time to ask questions about any changes that don't seem familiar.