You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+49Lines changed: 49 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,54 @@ Contributions are always welcome, no matter how large or small!
4
4
5
5
We want this community to be friendly and respectful to each other. Please follow it in all your interactions with the project. Before contributing, please read the [code of conduct](./CODE_OF_CONDUCT.md).
6
6
7
+
## Setting Up the Second Remote (GitHub)
8
+
9
+
Our project uses two remotes:
10
+
11
+
**GitLab**: The main repository where development happens.
12
+
**GitHub**: Used to deploy the documentation to Vercel.
13
+
14
+
If you make changes to the **documentation**, you will need to push your changes to the GitHub repository to trigger the deployment process.
15
+
16
+
Steps to Add the Second Remote
17
+
Open a terminal and navigate to the project's root directory.
18
+
19
+
Run the following command to add the GitHub remote:
The GitHub repository is integrated with Vercel for automatic deployment of the documentation. Pushing to GitHub ensures that the latest documentation changes are deployed seamlessly.
28
+
29
+
Whenever you update the documentation, it’s important to push your changes to both remotes:
30
+
31
+
**origin (GitLab)**: For collaboration and code review.
32
+
**github**: For triggering the deployment of documentation to Vercel.
33
+
34
+
You can manually push to both remotes with the following commands:
35
+
36
+
```
37
+
git push origin <branch-name>
38
+
git push github <branch-name>
39
+
```
40
+
However, to simplify this process, we’ve added a handy alias to automate it.
41
+
42
+
Using the Alias
43
+
To push the current branch to both remotes:
44
+
45
+
```
46
+
yarn push-to-remotes
47
+
```
48
+
49
+
To specify a branch explicitly:
50
+
51
+
```
52
+
npm run push-to-remotes -- <branch-name>
53
+
```
54
+
7
55
## Development workflow
8
56
9
57
To get started with the project, run `yarn` in the root directory to install the required dependencies for each package:
@@ -100,6 +148,7 @@ The `package.json` file contains various scripts for common tasks:
100
148
-`yarn example start`: start the Metro server for the example app.
101
149
-`yarn example android`: run the example app on Android.
102
150
-`yarn example ios`: run the example app on iOS.
151
+
-`yarn push-to-remotes`: push branch to origin and github remotes.
Installation instructions and documentation can be found on the [react-native-material-components](https://react-native-material-components.vercel.app/)
0 commit comments