Anshika-Jain02 / codesetgo

Open Source Website of CodeSetGo

CodeSetGo👩‍💻👨‍💻

Contributions Accepted under GSSoC '23

CodeSetGo is a place for Tech Enthusiasts to learn the latest technology in the comfort and convenience of their homes! It's the community of learners, developers, cryptographers and enthusiastic folks who are engaged toward the brighter future of technology and innovations! The Tech interested students and professionals are all welcomed!

Visit Our Website💻

So, here you go! Contribute to the Open Source Website of CodeSetGo Community 🤩 Excited?

Tech Used

Sneak Peek of the Website:

Contribution Guidelines 🏗

Step 1: Find an issue

• Take a look at the Existing Issues or create your own Issues!
• Wait for the Issue to be assigned to you after which you can start working on it.
• Note: Every change in this project should/must have an associated issue.

Step 2: Fork the Project

• Fork this Repository. This will create a Local Copy of this Repository on your Github Profile. Keep a reference to the original project in the upstream remote.

$ git clone https://github.com/<your-username>/codesetgo-website
$ cd codesetgo-website
$ git remote add upstream https://github.com/agamjotsingh18/codesetgo-website

• If you have already forked the project, update your copy before working.

$ git remote update
$ git checkout <branch-name>
$ git rebase upstream/<branch-name>

Step 3: Branch

Create a new branch. Use its name to identify the issue you addressing.

# It will create a new branch with the name Branch_Name and switch to that branch 
$ git checkout -b branch_name

Step 4: Work on the issue assigned

• Work on the issue(s) assigned to you.
• Add all the files/folders needed.

# To start the server in development mode
$ npm run dev

# To start the server in production mode
$ npm start

• After you've made changes or made your contribution to the project add changes to the branch you've just created by:

# To add all new files to branch Branch_Name
$ git add.

Step 5: Commit

• To commit give a descriptive message for the convenience of the reviewer by:

# This message gets associated with all files you have changed
$ git commit -m "message"

Step 6: Push the changes

# To push your work to your remote repository
$ git push -u origin Branch_Name

Step 7: Create a Pull Request

• Go to your repository in the browser and click on compare and pull request. Then add a title and description to your pull request that explains your contribution.

• Voila! Your Pull Request has been submitted and will be reviewed by the moderators and merged.🥳

Contributors ✨

Thanks goes to these wonderful people :

This project follows the all-contributors specification. Contributions of any kind welcome!

---

Back to top