mvdan.cc / cue
this repo has no description
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

CONTRIBUTING: clarify two sections

Various edits to the contribution guide, including:

- Linking to the install go-codereview section
- Adding an example of a cross repo reference

Signed-off-by: Cedric Charly <cedric.charly@gmail.com>
Change-Id: I859f6ae7f8ffd27f09948b3bb0cb41d97b2b548c
Reviewed-on: https://review.gerrithub.io/c/cue-lang/cue/+/1171864
Unity-Result: CUE porcuepine <cue.porcuepine@gmail.com>
TryBot-Result: CUEcueckoo <cueckoo@cuelang.org>
Reviewed-by: Paul Jolly <paul@myitcv.io>
Reviewed-by: Daniel Martí <mvdan@mvdan.cc>

authored by

Cedric Charly and committed by
Daniel Martí d947a69c a060f85d

+3 -3
+3 -3
CONTRIBUTING.md
··· 322 322 - **Step 0**: Review the guidelines on [Good Commit Messages](#good-commit-messages), [The Review Process](#the-review-process) and [Miscellaneous Topics](#miscellaneous-topics) 323 323 - **Step 1**: Decide which email address you want to use for contributions. 324 324 - **Step 2**: Set up a [GerritHub](http://gerrithub.io/) account. 325 - - **Step 3**: Install `git-codereview` 325 + - **Step 3**: [Install `git-codereview`](#step-3-install-the-git-codereview-command) 326 326 - **Step 4**: Clone the CUE repository locally. 327 327 328 328 ··· 628 628 applied. 629 629 630 630 631 + All issues are tracked in the main repository's issue tracker. 631 632 If you are sending a change against a subrepository, you must use the 632 633 fully-qualified syntax supported by GitHub to make sure the change is linked to 633 - the issue in the main repository, not the subrepository. All issues are tracked 634 - in the main repository's issue tracker. The correct form is "Fixes #159". 634 + the issue in the main repository, not the subrepository (eg. "Fixes cue-lang/cue#999"). 635 635 636 636 637 637