Instructions how to update Stride code base

[VaclavElias]

Stride Contributor Workflow

Make sure you are familiar with our main GitHub Stride page. The following steps might work for you in many scenarios if you are new to Stride. The advance contributors can skip some steps or you might be asked to do PR so the reviewers and approvers can see the code changes easier, and discuss your contribution directly through PR comments.

1. Create a new Issue and Discuss with the community or take ownership of existing issue
   or run it from VS's toolbar.
2. Fork this repository or clone directly git lfs clone https://github.com/stride3d/stride.git
   • make sure LFS (Large File Storage) is used
3. Open \build\Stride.sln with Visual Studio 2022 and build Stride.GameStudio (it should be the default startup project)
4. Create and checkout a new branch e.g. 457-fsharp-fix
   • the branch name can be IssueNumber-short-issue-title
5. Update SharedAssemblyInfo.cs temporarily to create a test version for your local NuGet packages   
   • Make sure the number is higher than existing public NuGet number   
   • Example PublicVersion = "4.1.1.0-fix457"
6. Make updates in the Stride code, fixing an issue or adding a new feature code
7. Build project
8. Packages should appear in %localappdata%\Stride\NugetDev
   • This path should be also in your VS Package Sources
9. Update Stride NuGet packages in your application to 4.1.1.0-fix457
10. Test, test, test
11. Commit changes in your branch
12. Create PR, follow the PR guide
    • make sure you get the PublicVersion to the original state as the maintainers will take care of correct versioning. We only used it locally for our development.

In the F# example, add 
Snippet<PackageReference Include="Stride.Core.Assets.CompilerApp" Version="4.1.1.0-fix457" IncludeAssets="build;buildTransitive" />

[VaclavElias]

Not sure why I added it here. Probably would need to go to Stride Docs..