Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

This is similar or the same as #23181 however it will be a new article based of #35725

What changes are you suggesting?

Give as much detail as you can to help us understand the change you want to see.
Because there's no documentation on how to properly handle Rust beyond the starter workflow I'd like to work on adding the guide, based on the work I do on #35725 for implementation (Likely it will be various PRs to make it reviewable)

My goal is to have this documented, so It can be reused further by at least community GH (i.e no self hosted runners for now or enterprise features)

Introduce a new guide, detailed in #35725 which can be the bare minimum; so rust is covered in a similar fashion as Golang is.

Additional information

I see a comment from @skedwards88 from: #23181 (comment)

• adhere to best practices: If the team does not feel that is meets our standards, we may close the PR.
• Team needs proof of runs:
  • https://github.com/foursixnine/cndk8/actions/runs/12445187630/job/34746246005
• Make PR work smaller, so work is reviewable by the team at github
  • Consider that Add instructions for building and testing with Rust #35725 can be the bare minimum

open questions:

• Question for GH team: is a rust registry similar to crates.io going to be provided by GH or do we use crates.io like https://docs.github.com/en/actions/use-cases-and-examples/building-and-testing/building-and-testing-python#publishing-to-pypi does for python?
• Is there anything right now that isn't covered by the points above?