diff options
| author | Guillaume Melquiond | 2018-10-05 08:38:17 +0200 |
|---|---|---|
| committer | Guillaume Melquiond | 2018-10-05 08:38:17 +0200 |
| commit | 6f56c46a8b2383c4c7cb2e10c24a5e5a3c2191fb (patch) | |
| tree | a88a2d1008b938e2494ec7735a862459c3f91d54 /dev/doc | |
| parent | 24c4c71236a6b12e9af6e8505c98e3ef1becb32a (diff) | |
Rename CHANGES to CHANGES.md.
Diffstat (limited to 'dev/doc')
| -rw-r--r-- | dev/doc/MERGING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/dev/doc/MERGING.md b/dev/doc/MERGING.md index c0cd9c8cdd..000f21c254 100644 --- a/dev/doc/MERGING.md +++ b/dev/doc/MERGING.md @@ -54,7 +54,7 @@ those external projects should have been prepared (cf. the relevant sub-section in the [CI README](../ci/README.md#Breaking-changes) and the PR can be tested with these fixes thanks to ["overlays"](../ci/user-overlays/README.md). -Moreover the PR must absolutely update the [`CHANGES`](../../CHANGES) file. +Moreover the PR must absolutely update the [`CHANGES.md`](../../CHANGES.md) file. If overlays are missing, ask the author to prepare them and label the PR with the [needs: overlay](https://github.com/coq/coq/labels/needs%3A%20overlay) label. @@ -93,7 +93,7 @@ When the PR has conflicts, the assignee can either: In both cases, CI should be run again. -In some rare cases (e.g. the conflicts are in the CHANGES file), it is ok to fix +In some rare cases (e.g. the conflicts are in the `CHANGES.md` file), it is ok to fix the conflicts in the merge commit (following the same steps as below), and push to `master` directly. Don't use the GitHub interface to fix these conflicts. |