... | @@ -66,7 +66,7 @@ Fill the fields in as follows: |
... | @@ -66,7 +66,7 @@ Fill the fields in as follows: |
|
| Source (from) branch | Should already be set to your CR branch - leave this unchanged. | `cr/102232-1/987` |
|
|
| Source (from) branch | Should already be set to your CR branch - leave this unchanged. | `cr/102232-1/987` |
|
|
| Target (to) branch | **This is important:** This will be set to `main` be default, which is wrong. You **must change it** otherwise it will cause issues for the TO and automated testing. Click "change branches" at the top of the form, and set the "Target" branch to the correct plenary meeting branch. Then click "Compare branches and continue". | `meeting/LI60` |
|
|
| Target (to) branch | **This is important:** This will be set to `main` be default, which is wrong. You **must change it** otherwise it will cause issues for the TO and automated testing. Click "change branches" at the top of the form, and set the "Target" branch to the correct plenary meeting branch. Then click "Compare branches and continue". | `meeting/LI60` |
|
|
| Title | `{Deliverable} CR {CR number} - {Title of your CR}` | `TS 102 232-1 CR987 - My First CR` |
|
|
| Title | `{Deliverable} CR {CR number} - {Title of your CR}` | `TS 102 232-1 CR987 - My First CR` |
|
|
| Description | A human readable description of your change. We suggest using the abstract or "reason for change" from your CR coversheet. It is *very helpful* if you include the Tdoc number of your CR in here, so that we can correlate between the Forge and the TCLI portal! | |
|
|
| Description | A human readable description of your change. We suggest using the abstract or "reason for change" from your CR coversheet. It is _very helpful_ if you include the Tdoc number of your CR in here, so that we can correlate between the Forge and the TCLI portal! | |
|
|
| Assignee | Click the "Assign to me" button to assign the MR to yourself | [@canterburym](/rep/canterburym) |
|
|
| Assignee | Click the "Assign to me" button to assign the MR to yourself | [@canterburym](/rep/canterburym) |
|
|
| Reviewer | Leave this unchanged | |
|
|
| Reviewer | Leave this unchanged | |
|
|
| Milestone | Leave this unchanged | |
|
|
| Milestone | Leave this unchanged | |
|
... | @@ -131,9 +131,15 @@ The commit hash turns up in lots of places. If you have just made a Merge Reques |
... | @@ -131,9 +131,15 @@ The commit hash turns up in lots of places. If you have just made a Merge Reques |
|
|
|
|
|
![Commit hash](../img/commithash.png)
|
|
![Commit hash](../img/commithash.png)
|
|
|
|
|
|
Copy this hash and refer to it in the "Comments" section of your CR.
|
|
Copy this hash and refer to it, and the Merge Request, in the "Comments" section of your CR.
|
|
|
|
|
|
> Even better, copy the URL associated with the commit hash. Click on either the link in the CI/CD pipeline report or on the title of the latest commit in the "commit" section. This takes you to a page that displays the commit. Referencing the URL in the CR form makes it easy for readers to see your changes
|
|
For consistency, CR authors should adopt the following convention when writing the text to go in the "Comments" field:
|
|
|
|
|
|
|
|
> This CR is associated with the following changes in the Forge:
|
|
|
|
>
|
|
|
|
> Merge Request: {_merge request number_}
|
|
|
|
>
|
|
|
|
> Commit hash: {_commit hash_}
|
|
|
|
|
|
For more information, see [CR form conventions](Conventions/CR-form-conventions)
|
|
For more information, see [CR form conventions](Conventions/CR-form-conventions)
|
|
|
|
|
... | | ... | |