|
2 | 2 | title: "Contribution" |
3 | 3 | description: "Pull requests (PRs) are the best ways to propose changes to a project repository. At Layer5 org, we use the Github Flow." |
4 | 4 | type: Handbook |
| 5 | +contents: |
| 6 | + - id: 0 |
| 7 | + link: "#Clone your fork" |
| 8 | + text: "Clone your fork" |
| 9 | + - id: 1 |
| 10 | + link: "#Checkout a new branch" |
| 11 | + text: "Checkout a new branch" |
| 12 | + - id: 2 |
| 13 | + link: "#Commit your changes" |
| 14 | + text: "Commit your changes" |
| 15 | + - id: 3 |
| 16 | + link: "#Sign-off commits" |
| 17 | + text: "Sign-off commits" |
| 18 | + - id: 4 |
| 19 | + link: "#Push changes to Github" |
| 20 | + text: "Push changes to Github" |
| 21 | + - id: 5 |
| 22 | + link: "#Create a pull request" |
| 23 | + text: "Create a pull request" |
5 | 24 | --- |
6 | 25 |
|
7 | 26 | import { Container } from "../../../reusecore/Layout"; |
8 | 27 | import Code from "../../../components/CodeBlock"; |
9 | | -import IntraPage from "../../../components/handbook-navigation/intra-page"; |
10 | 28 | import signoffImg from "./git-signoff-vscode.webp"; |
11 | 29 | import compareImg from "./compare-and-pr.webp"; |
12 | 30 | import createPrImg from "./create-pr.webp"; |
13 | 31 |
|
14 | | -export const contents = [ |
15 | | - { id: 0, link: "#Clone your fork", text: "Clone your fork" }, |
16 | | - { id: 1, link: "#Checkout a new branch", text: "Checkout a new branch" }, |
17 | | - { id: 2, link: "#Commit your changes", text: "Commit your changes" }, |
18 | | - { id: 3, link: "#Sign-off commits", text: "Sign-off commits" }, |
19 | | - { id: 4, link: "#Push changes to Github", text: "Push changes to Github" }, |
20 | | - { id: 5, link: "#Create a pull request", text: "Create a pull request" }, |
21 | | -]; |
22 | 32 |
|
23 | 33 |
|
24 | 34 | <h2 className="heading-top">General contribution flow</h2> |
@@ -157,4 +167,3 @@ At [Layer5](https://layer5.io/), we usually suggest to contributors that they as |
157 | 167 | - **Requesting Reassignment:** If you are interested in working on an issue that is already assigned to someone else, it's important to respect their efforts and contributions. First, politely reach out to the assignee and express your interest in collaborating on the issue. Discuss the possibility of working together or sharing the workload. If the assignee agrees or is open to collaboration, you can proceed. If the assignee is not responsive or there has been no progress on the issue for a long time and the issue aligns with your skills and interests, kindly request reassignment from the maintainers, providing a clear and courteous explanation for the request. |
158 | 168 | <br/>**Example:** [[chore] update Go to 1.21, and update relevant pkgs #169](https://github.com/meshery/meshery-nsm/issues/169) |
159 | 169 |
|
160 | | -<IntraPage contents={contents} /> |
|
0 commit comments