Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added authentication system and chat group system #123

Merged
merged 8 commits into from
Jun 2, 2021
Merged

added authentication system and chat group system #123

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
214f20e
added authentication system and chat group system
robinsingh-ai Mar 28, 2021
3a1547e
added react-messaging-app
robinsingh-ai Jun 1, 2021
462b987
resolved conflicting files
robinsingh-ai Jun 1, 2021
1e6be5f
resolved conflict
robinsingh-ai Jun 1, 2021
eddcfae
Reverted LICENSE
robinsingh-ai Jun 1, 2021
4932b01
removed licence.txt
robinsingh-ai Jun 1, 2021
90e6434
deleted images
robinsingh-ai Jun 1, 2021
61aab70
added images
robinsingh-ai Jun 1, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 24 additions & 3 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,25 @@
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.

# dependencies
/node_modules
node_modules
src/Thumbs.db
.eslintcache
/.pnp
.pnp.js

# testing
/coverage

# production
/build

# misc
.DS_Store
.env.local
.env.development.local
.env.test.local
.env.production.local

npm-debug.log*
yarn-debug.log*
yarn-error.log*

.eslintcache
106 changes: 1 addition & 105 deletions Contributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Contributing Guidelines
# Contributing Guidelines

## Forking
If you are assigned to an issue or if you want to test the project in your local system, you should fork the project so that you can make changes in your personal space without affecting the orignal repository 😊 .
Expand All @@ -20,107 +20,3 @@ If you successfully made your first contribution, then you must add your name in

## Nervous ??
Don't feel nervous if this is your first contribution. Every expert was once a beginner. Feel free to reach out to me for any problem on my social media handles which are given in the readme file 😊 .

## How to Contribute

## GIT AND GITHUB

Before continuing we want to clarify the difference between Git and Github. Git is a version control system(VCS) which is a tool to manage the history of our Source Code. GitHub is a hosting service for Git projects.

We assume you have created an account on Github and installed Git on your System.

Now tell Git your name and E-mail (used on Github) address.

$ git config --global user.name "YOUR NAME"
$ git config --global user.email "YOUR EMAIL ADDRESS"


This is an important step to mark your commits to your name and email.

### FORK A PROJECT -

You can use github explore - https://github.com/explore to find a project that interests you and match your skills. Once you find your cool project to workon, you can make a copy of project to your account. This process is called forking a project to your Github account. On Upper right side of project page on Github, you can see -

<p align="center"> <img src="https://i.imgur.com/P0n6f97.png"> </p>

Click on fork to create a copy of project to your account. This creates a separate copy for you to workon.

### FINDING A FEATURE OR BUG TO WORKON -

Open Source projects always have something to workon and improves with each new release. You can see the issues section to find something you can solve or report a bug. The project managers always welcome new contributors and can guide you to solve the problem. You can find issues in the right section of project page.

<p align="center"> <img src="https://i.imgur.com/czVjpS7.png"> </p>

### CLONE THE FORKED PROJECT -

You have forked the project you want to contribute to your github account. To get this project on your development machine we use clone command of git.

```$ git clone https://github.com/<your-account-username>/<your-forked-project>.git```
Now you have the project on your local machine.

### ADD A REMOTE (UPSTREAM) TO ORIGINAL PROJECT REPOSITORY

Remote means the remote location of project on Github. By cloning, we have a remote called origin which points to your forked repository. Now we will add a remote to the original repository from where we had forked.

$ cd <your-forked-project-folder>
$ git remote add upstream https://github.com/<author-account-username>/<project>.git

You will see the benefits of adding remote later.

### SYNCHRONIZING YOUR FORK -

Open Source projects have a number of contributors who can push code anytime. So it is necessary to make your forked copy equal with the original repository. The remote added above called Upstream helps in this.


$ git checkout master
$ git fetch upstream
$ git merge upstream/master
$ git push origin master


The last command pushes the latest code to your forked repository on Github. The origin is the remote pointing to your forked repository on github.

### CREATE A NEW BRANCH FOR A FEATURE OR BUGFIX -

Normally, all repositories have a master branch which is considered to remain stable and all new features should be made in a separate branch and after completion merged into master branch. So we should create a new branch for our feature or bugfix and start working on the issue.

```$ git checkout -b <feature-branch>```
This will create a new branch out of master branch. Now start working on the problem and commit your changes.

$ git add --all
$ git commit -m "<commit message>"


The first command adds all the files or you can add specific files by removing -a and adding the file names. The second command gives a message to your changes so you can know in future what changes this commit makes. If you are solving an issue on original repository, you should add the issue number like #35 to your commit message. This will show the reference to commits in the issue.

### REBASE YOUR FEATURE BRANCH WITH UPSTREAM-

It can happen that your feature takes time to complete and other contributors are constantly pushing code. After completing the feature your feature branch should be rebase on latest changes to upstream master branch.

$ git checkout <feature-branch>
$ git pull --rebase upstream master

Now you get the latest commits from other contributors and check that your commits are compatible with the new commits. If there are any conflicts solve them.

### SQUASHING YOUR COMMITS-

You have completed the feature, but you have made a number of commits which make less sense. You should squash your commits to make good commits.

```$ git rebase -i HEAD~5```
This will open an editor which will allow you to squash the commits.

### PUSH CODE AND CREATE A PULL REQUEST -

Till this point you have a new branch with the feature or bugfix you want in the project you had forked. Now push your new branch to your remote fork on github.

```$ git push origin <feature-branch>```

Now you are ready to help the project by opening a pull request means you now tell the project managers to add the feature or bugfix to original repository. You can open a pull request by clicking on green icon -

<p align="center"> <img src="https://i.imgur.com/aGaqAD5.png"> </p>

Remember your upstream base branch should be master and source should be your feature branch. Click on create pull request and add a name to your pull request. You can also describe your feature.

Awesome! You have made your first contribution. If you have any doubts please let me know in the comments.

#### BE OPEN!
10 changes: 1 addition & 9 deletions Contributors.md
100755 → 100644
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,4 @@ Jwright707 <kfcpcc@gmail.com> <br/>
Pekebyte <pedrom@pekebyte.com> <br/>
wandering-sage <shivam4503@gmail.com> <br/>
sagrawal9689 <sagrawal9689@gmail.com> <br/>
JatinAgrawal94 <jatinagrawal0801@gmail.com> <br/>
Aniket1103 <aniketbagayatkar02@gmail.com> <br/>
yokesh004 <balayokeshmani@gmail.com> <br/>
Himanshu16Singh <hsnice16@gmail.com> <br/>
shreyanshi16 <shahshreyanshi01@gmail.com> <br/>
Arshanshagarwal <arshanshagarwal1@gmail.com> <br/>
dig9074vijay <dig9074vijay@gmail.com> <br/>
Rohank2502 <rohank2502@gmail.com> <br/>
vieee <dgyadav1782000@gmail.com> <br/>
JatinAgrawal94 <jatinagrawal0801@gmail.com>
Empty file modified LICENSE.txt
100755 → 100644
View file
Open in desktop
Empty file.
21 changes: 1 addition & 20 deletions README.md
100755 → 100644
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,12 @@
# React-Messenger-App
![logo](https://miro.medium.com/max/3176/1*h-xRzZOCHk8jTlEa8M42GA.png)
##
[![forthebadge](https://forthebadge.com/images/badges/open-source.svg)](https://forthebadge.com) [![forthebadge](https://forthebadge.com/images/badges/built-with-love.svg)](https://forthebadge.com) [![forthebadge](https://forthebadge.com/images/badges/made-with-crayons.svg)](https://forthebadge.com) [![forthebadge](https://forthebadge.com/images/badges/made-with-javascript.svg)](https://forthebadge.com)
[![forthebadge](https://forthebadge.com/images/badges/built-with-love.svg)](https://forthebadge.com) [![forthebadge](https://forthebadge.com/images/badges/made-with-crayons.svg)](https://forthebadge.com) [![forthebadge](https://forthebadge.com/images/badges/made-with-javascript.svg)](https://forthebadge.com)

This is a Messenger App, made with react, styled with the help of material-ui and deployed with the help of firebase.

Here is the link to the deployed app :- https://mui-message.firebaseapp.com

### We are now part of GSSoC 2021 !
[![GSSoC](https://raw.githubusercontent.com/GirlScriptSummerOfCode/MentorshipProgram/master/GSsoc%20Type%20Logo%20Black.png)](https://gssoc.girlscript.tech)
We got accepted for the GSSoc 2021 and activelty looking for new participants,please feel free to ask questions in the discussion section of this repository and if you want to be our mentor please mention in the discussion.

## Motive

This Repository is created with a motive to guide beginners with the open-source and with big react projects. I have already created some issues for the beginners so that they can work on them and even make there first contribution in this repository.
Expand All @@ -36,7 +32,6 @@ I am Writing down the Dependencies for beginners, so that they can look into it
* [Twitter](https://twitter.com/bahldhairya)
* [Medium](https://medium.com/@dhairyabahl5)
* [Gmail](dhairyabahl5@gmail.com)
* [LinkedIn](https://www.linkedin.com/in/dhairya-bahl)

## Show your support

Expand All @@ -52,17 +47,3 @@ Kindly refer to the contributing.md file. All the contributing guidelines are wr

## 3. Is there any need to assign myself to the issue before starting to work on the issue ?
It is better to wait until you are assigned to the issue. Although if you are sure that no-one is working on the issue then you can start working on the issue.

<h2>Contributors:</h2>

### Credits goes to these people:✨

<table>
<tr>
<td>
<a href="https://github.com/DhairyaBahl/React-Messenger-App/graphs/contributors">
<img src="https://contrib.rocks/image?repo=DhairyaBahl/React-Messenger-App" />
</a>
</td>
</tr>
</table>
Loading