Unified readme + Use local gem (remote is not compatible anymore) #2
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
Signed-off-by: guillaume-haerinck <[email protected]>
|
Change is visible here : https://github.com/guillaume-haerinck/O3DE-FirstPersonInteractionToolkit/tree/unified_readme |
|
Thanks for the help 🙏 |
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.
First take on an unified readme format used accross every O3DE samples (and checked that the project still runs correctly on the release of 23.10.3)
The goal being to make the samples more accessible to the users. Both by updating the project's readme, adding a version check and linking them in O3DE showcase and doc pages. Task tracked via this issue : o3de/o3de.org#2549
I also modified the project.json to target your local Gem of FirstPersonController. The latest version does not seems to be totally compatible anymore (as a future improvement, it could be put as a git submodule)