Skip to content

doc: put landing specifics in details tag

Rodrigo Muino Tomonari requested to merge github/fork/Trott/details-collab-guide into master

Showing all the steps isn't usually useful and in makes it seem like the collaborator is meant to follow the manual steps. I've seen this happen during at least one onboarding. The section is also a bit long to comfortably scroll over quickly to find the next section.

Let's put those steps in a details block to make it more obvious that it is there for unusual situations only.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports