This website contains a list of open source events and hackathon.
This website contains a list of open source events and hackathons. They are in a proper month wise timeline so the user does not face difficulty while searching through the open source events. Most of the times students want to participate in the events but they don't know the dates or the event details. This repo contains links of the events and when are the events going to take place.
Home Page
Detail of events according the month
When a repository is cloned, it has a default remote called origin
that points to your fork on GitHub, not the original repository it was forked from. To keep track of the original repository, you should add another remote named upstream
:
git remote -v
to check the status you should see something like the following:origin https://github.com/YOUR_USERNAME/OpenSourceEvents-Frontend.git (fetch)
origin https://github.com/YOUR_USERNAME/OpenSourceEvents-Frontend.git (push)
upstream
:git remote add upstream https://github.com/Catalyst-CSE/OpenSourceEvents-Frontend.git
git remote -v
again to check the status, you should see something like the following:origin https://github.com/YOUR_USERNAME/OpenSourceEvents-Frontend.git (fetch)
origin https://github.com/YOUR_USERNAME/OpenSourceEvents-Frontend.git (push)
upstream https://github.com/Catalyst-CSE/OpenSourceEvents-Frontend.git (fetch)
upstream https://github.com/Catalyst-CSE/OpenSourceEvents-Frontend.git (push)
git fetch upstream master
git rebase upstream/master
git checkout master
.git pull --rebase upstream master
.git checkout -b branch_name
.git add file_name
(avoid using git add .
).git commit -m "Message briefly explaining the feature"
.git commit --amend
.git push origin branch-name
.git commit --amend
, push again and the pull request will edit automatically.git rebase -i origin/master~n master
(having n number of commits).git push origin branchname --force
.- git checkout master
- git fetch --all --prune
- git merge --ff-only upstream/master
- git push origin master
- Pick an open issue from the issue list and claim it in the comments. After approval fix the issue and send us a pull request (PR).
- All the PR’s need to be sent to the appropriate branch (usually "master").
- You can create a new issue and send a pull request.
- Please go through our issue list first (open as well as closed) and make sure the issue you are reporting does not replicate an issue already reported. If you have issues on multiple pages, report them separately. Do not combine them into a single issue.
You can reach the maintainers and our community on Catalyst-discord. If you are interested in contributing to the OpenSourceEvents-Frontend, we have a dedicated stream for this project #OpenSourceEvents-Frontend, where you can ask questions and interact with the community, join with us!
💜 Thanks Thanks to our many contributors.