... | ... | @@ -13,13 +13,13 @@ Set the details as follows: |
|
|
| Branch name | Start with `draft/` followed by something descriptive. A good convention to follow is using your initials and the spec you are drafting a change for| `draft/msc_103120` |
|
|
|
| Create from | Choose the [current meeting branch](Conventions/Branching-convention), if available, otherwise `main` | `main` |
|
|
|
|
|
|
> If you create a draft branch from `main` rather than a current meeting branch, you may need to take some extra steps when you come to [turn your draft into a real CR](#convert-a-draft-branch-to-a-cr-branch). If at all possible, create from the latest meeting branch. If there is no current meeting branch, and you think there should be one, contact the [maintainers](Maintainers.md).
|
|
|
> If you create a draft branch from `main` rather than a current meeting branch, you may need to take some extra steps when you come to [turn your draft into a real CR](#convert-a-draft-branch-to-a-cr-branch). If at all possible, create from the latest meeting branch. If there is no current meeting branch, and you think there should be one, contact the [maintainers](Maintainers).
|
|
|
|
|
|
Then click "Create branch"
|
|
|
|
|
|
## Make changes as normal
|
|
|
|
|
|
Make your changes [exactly like you would for a normal CR](How-To/Create-a-CR.md#make-your-changes), either via the Forge Web UI or via a local clone of the repository.
|
|
|
Make your changes [exactly like you would for a normal CR](How-To/Create-a-CR#make-your-changes), either via the Forge Web UI or via a local clone of the repository.
|
|
|
|
|
|
The CI/CD pipeline will still run after each commit, meaning that your draft changes will have the same ASN.1 and XSD checks run on them. This means that a draft branch can help you debug your schema changes while you are still drafting your CR.
|
|
|
|
... | ... | |