Repository navigation
docs: point contributors at dev clones - #7
Merged
Merged
Conversation
This file contains hidden or 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
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.
What and why
Adds a "Where to work" note to CONTRIBUTING.md. It tells contributors to clone this repo into the
dev/folder of a Nova-Collected clone (e.g.Nova/dev/frontend) and branch fromdev, and never to work in theprod/orpi/submodules, which are overwritten on release. Also repoints the testing-procedure reference from the olddocs/testing-procedure.mdpath to its current location in Nova-Collected (docs/development/testing-procedure.md).How was this tested?
Docs only, so no level applies. I read the rendered CONTRIBUTING.md and checked that the new testing-procedure link points at the file's current path in Nova-Collected.
Hardware impact
hardware-risklabel; a lead must approve!, link the matching PRs:Checklist
dev(ormainfor a release/hotfix, or with a reason given above).envfiles or build output committed