Welcome to Hacktoberfest 2021, Contributors

Astro Credence

This is code repository for a simple analytics visualization site for Codeforces online judge users using Codeforces API.

This is code repository for a project that I am working. Astrocredence is a platform where your thoughts are shared, acknowledged and debated upon? A platform where you can portray yourself,your art and even sell it without the hassle of finding the right digital market?

Prerequisites:

• Install git in your machine.
• Have basic command line experiance.
• have knowledge of basic Javascript, HTML, CSS

Resources to follow to contribute to this project or any open source project

1. Read this guide to open-source contribution.

2. To add the necessary contribution that will get your Pull Request accepeted refer CONTRIBUTING.md file.

Claim an Issue

Comment on the issue. In case of no activity on the issue even after 2 days, the issue will be reassigned. If you have difficulty approaching the issue, feel free to ask on our slack channel.

Communication

If you have any queries or suggestions, please use the discord channel of Geek Editor FrontEnd.

How to contribute?

• Fork this repo
• Create a new file in "Contributions" folder
• Add any code in any language you like
• Push PR
• Follow Developer & Star the repo
• All done!

Rules and Regulations

1. Pull requests can be submitted to any opted-in repository on GitHub or GitLab

2. The pull request must contain commits you made yourself.

3. If a maintainer reports your pull request as spam, it will not be counted toward your participation in Hacktoberfest.

4. If a maintainer reports behavior that’s not in line with the project’s code of conduct, you will be ineligible to participate.

5. To get a shirt, you must make four approved pull requests (PRs) on opted-in projects between October 1-31 in any time zone.

6. This year, the first 50,000 participants can earn a T-shirt.

Examples of low quailty contributions

• Pull requests that are automated e.g. scripted opening pull requests to remove whitespace / fix typos / optimize images.

• Pull requests that are disruptive e.g. taking someone else's branch/commits and making a pull request.

• Pull requests that are regarded by a project maintainer as a hindrance vs. helping.

• Something that's clearly an attempt to simply +1 your pull request count for October.

• Last but not least, one pull request to fix a typo is fine, but 5 pull requests to remove a stray whitespace is not.