Skip to content

Commit 31abed2

Browse files
Merge branch 'readme' into 'main'
docs: updated readme and contribution See merge request react-native/react-native-material-components!27
2 parents 68116f6 + 49022e0 commit 31abed2

File tree

2 files changed

+53
-5
lines changed

2 files changed

+53
-5
lines changed

CONTRIBUTING.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,54 @@ Contributions are always welcome, no matter how large or small!
44

55
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).
66

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:
20+
21+
```
22+
git remote add github https://github.com/computools-anastasiia-nahaiska/react-native-material-components.git
23+
```
24+
25+
### Pushing Changes to Both Remotes
26+
27+
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+
755
## Development workflow
856

957
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:
100148
- `yarn example start`: start the Metro server for the example app.
101149
- `yarn example android`: run the example app on Android.
102150
- `yarn example ios`: run the example app on iOS.
151+
- `yarn push-to-remotes`: push branch to origin and github remotes.
103152

104153
### Sending a pull request
105154

README.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
# @computools/react-native-material-components
22

3-
Computools react native material components package
3+
Computools' React Native material components package.
44

5-
<!-- Todo: add link to documentation website -->
6-
![Documentation]()
7-
![Material desgin Figma](https://www.figma.com/design/MY4zoWhMQUMOMIfBGcgSpy/Material-3-Design-Kit-(Community)?node-id=47909-2&p=f&t=Fo0xFwhmWhLMqS8Z-0)
8-
![Material icons design Figma](https://www.figma.com/design/siKJo238QbcA9I2EqYMZ9y/Material-Design-Icons-(Community)?node-id=2402-2207&node-type=canvas&t=xqHD7AwdyHpKWsur-0)
5+
# Documentation
6+
7+
Installation instructions and documentation can be found on the [react-native-material-components](https://react-native-material-components.vercel.app/)
98

109
## Contributing
1110

0 commit comments

Comments
 (0)