docs: use the new [!NOTE]
syntax (#10959)
* style-guide: use the new note syntax * MAINTAINERS: use the new note syntax, use full month names * CONTRIBUTING: use the new note syntax * maintainers-guide: use the new note syntax * CLIENT-SPECIFICATION: use the new note syntax * COMMUNITY-ROLES: use the new note syntax * git-terminal: use the new note syntax --------- Co-authored-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com>
This commit is contained in:
@@ -14,7 +14,8 @@ The overall process should look somewhat like this:
|
||||
3. Create a feature branch, e.g. named after the command you plan to edit:
|
||||
`git checkout -b {{branch_name}}`
|
||||
|
||||
> :warning: It is bad practice to submit a PR from the `main` branch of your forked repository. Please create pull requests from a well named feature branch.
|
||||
> [!WARNING]
|
||||
> It is bad practice to submit a PR from the `main` branch of your forked repository. Please create pull requests from a well named feature branch.
|
||||
|
||||
4. Make your changes (edit existing files or create new ones)
|
||||
|
||||
@@ -24,7 +25,8 @@ The overall process should look somewhat like this:
|
||||
6. Push the commit(s) to your fork:
|
||||
`git push origin {{branch_name}}`
|
||||
|
||||
> :warning: Please avoid force-pushing since it makes the review process harder.
|
||||
> [!WARNING]
|
||||
> Please avoid force-pushing since it makes the review process harder.
|
||||
|
||||
7. Go to the GitHub page for your fork and click the green "Compare & pull request" button.
|
||||
|
||||
|
Reference in New Issue
Block a user