Added my github profile to contributors.json

Description

Please refer the image, all input fields lose their selected value.

Description

The mobile navbar covers the first developer card information.

Current Behaviour:

Expected Behaviour:

Make sure that the navbar doesn't hide information for first developer card.

Acceptance criteria

• Navbar should be properly aligned
• Screenshot of the changes should be in the PR
• It should not break the desktop navbar

The icon of changing the theme color, is not showing in the range 340px to 320, and vertical alignment is a bit off

So when I was working on #133, I noticed some bugs:

• Navbar menu is not visible on mobile web version.

• and what is the purpose of this blank space below the footer?

I can work on this, assign me this issue I'll fix it.

Description

On the occasion of Hacktoberfest and to help beginners who have just started to get there hands dirty with GIt and Github, this repository is to guide newcomers and open source enthusiasts to come together and contribute.
The first issue is really simple, you only have to add the following fields in contributor.json file:

"<guthub_username>": {
   "country": "Your Country", // Required
   "name": "Your Name", // Required
   "linkedin": "linkedin URL", // Optional
   "twitter": "twitter URL", // Optional
   "website":"website or blog URL"//Optional
}

Here is a reference from an early contributor: #22

Steps

1. Fork the repository
2. Clone the repository you have forked (Appears in the repository section of your profile)
3. Checkout to a new branch. (Optional if you don't have a concept of branching)
4. Change in contributor.json add your information in the above json object. Note: Make sure you place your information in the correct order according to the GitHub user name in ascending order ignoring case sensivity. This is done to avoid many merge conflicts. If you don't want to do it manually, you can use the following command:

npx sort-json contributors.json --ignore-case

5. Commit the changes
6. Create a PR to the original repository
   Here's how to do it:
   Step 1: Go to Code section of forked repo an click on Pull request below the Code Button besides Compare Button
   Step 2: Make sure the following is branches are selected:

Here is a guide/lab if you haven't created any commits or PRs:
https://subeshbhandari.com/blog/git-and-github-practical-for-beginners

If you get stuck in any step feel free to tag me and request help

PS: Feel free to star the repository and follow me :)

After this, your PR will be reviewed and once all the checks pass it will be merged to master. The PR will we then labeled as hacktoberfest-approved

Outcome of this issue

• Collaboration and contribution to open source
• Experience continuous integration of code changes in a repository
• Be a part of Developer Community Stats

Repository Context

This repository shows the Github stats of every contributor that has contributed to the above file. In the future, more detailed stats will be shown for each individual contributor. For now, it only shows basic stats, for example, total contribution this year, followers, number of pull requests, repository count, etc. Once your PR gets merged it will be shown on the Website:
https://developer-community-stats.netlify.app/

Description

As the number of contributors is growing and it's quite hard to find one's own profile, we need a feature to sort and filter out users. It is to be done on the client-side.
The filterable fields are:

1. Github user name
2. User name
3. Country

The sortable fields are:

1. Country
2. Github user name
3. User name
4. Total commits (this year)
5. Followers

Acceptance criteria

• The above-listed fields should be filterable and sortable as listed.
• The filtering should be done on the client-side. (All the contributor data is present in UI as JSON)
• Add form fields to filter and sort.

Reference

src/pages/index.js

Description

Deploy site on code push to master

Acceptance criteria

• When code Is pushed to master the code should be deployed to netlify
• The build should happen in Github action

"<guthub_username>": {
"country": "Your Country", // Required
"name": "Your Name", // Required
"linkedin": "linkedin URL", // Optional
"twitter": "twitter URL", // Optional
"website":"website or blog URL"//Optional
}

Description

The internal links in the card shown on the home page don't point to the respective links. They instead redirect to the user's profile. We need to make sure that the links in Icon are clickable and point to respective pages. The problem is caused by nesting links within a link. Try to figure out a way to make both links interactable.

Acceptance criteria

• When clicked on the icon, the link should open
• When clicked on anywhere in the card except the icons, it should open the profile page of the user

Reference

src/components/DeveloperCard/index.jsx

Description

Since GitHub tokens can't be used in Github actions for PR coming from the forked repository, a mock was set up to build for those PRs. However the mock takes quite some time. And to speed up action build, remove the app build a part in

.github/workflows/contributor_spec.yaml:23

There will be a separate issue to handle cases where website build is necessary.

As the number of contributors grow, a single request to fetch all user data via Github Graphql API results in a timeout.
Breakdown the query to 20 user request per query.

Description

This repo is created to help beginners to take their first step into Open source contribution. This is also a place for developers all over the world to come together and view their Github profile stats. Currently only the stats of contributors who have contributed to contributors.json are show and the progress for showing detailed stats is going on.

About this issue

I need some suggestions about how to take this repository forward. What kind of activities to engage new developers or any feature requests.

Description

As the number of collaborators increases and the changes made can be breaking, it'll help out a lot to create a staging environment where we can test first and then deploy to production

Acceptance criteria

• Create a Github action workflow to run for the staging environment
• Create a URL for stating environment in netlify
• Choose branch staging

Prerequisites ⚠️⚠️⚠️

You must have completed Issue #259

Description

This is the second challenge. You will add a markdown file in directory readme-profiles named:

<github_username>.md

Add something about you and your showcases or projects. The information will be seen when you click on your stats on the home page.

Here is a reference for markdown https://github.com/subeshb1/developer-community-stats/blob/main/readme-profiles/subeshb1.md
You can also copy the content and simply replace the user's information with yours.

Steps

1. Fork the repository
2. Clone the repository you have forked (Appears in the repository section of your profile)
3. Checkout to a new branch. (Optional if you don't have a concept of branching)
4. Create a new file named <github_username>.md in readme-profiles directory.
5. Add some markdown with your information and show cases.
6. Commit the changes
7. Create a PR to the original repository
   Here's how to do it:
   Step 1: Go to Code section of forked repo an click on Pull request below the Code Button besides Compare Button
   Step 2: Make sure the following is branches are selected:

Here is a guide/lab if you haven't created any commits or PRs:
https://subeshbhandari.com/blog/git-and-github-practical-for-beginners

If you get stuck in any step feel free to tag me and request help

PS: Feel free to star the repository and follow me :)

Outcome of this issue

• Collaboration and contribution to open source
• Experience continuous integration of code changes in a repository
• Learn about markdown
• Get more experience in creating Pull requests and reviews.

Output

Once your PR is merged you will see your profile by clicking on your card as below:

Description

We need to add website link in github profile stats card. Choose a proper icon and layout

Description

The deploy action gets triggered on push to master. But it also runs when changes in Readme files and non deploy needing files.

Update the action to prevent deploy on pushes to those files:

.github/workflows/main_deploy.yaml

Currently, the profile page is opened on clicked anywhere on the card. Show a link after it hovers. For the profile page, the link should not be shown.

Description

Add icons on the footer for the following technologies with their respective links:

1. React
2. Gatsby
3. Github
4. Graphql

Add a text Made with followed by icons.

Acceptance criteria

• The icons should be visible in both dark and light themes
• The layout should have proper design. (Explore some examples)

Description

Since the application data is generated in the build time create a Github action to update the site every one day.

Description

When the Github icon on the navbar is clicked, direct it to this repository.

Description

To show all the contributors, create a website that shows the contributors listed in the JSON file.

Acceptance criteria

• List all the contributors listed in contributor.js file
• Create a website to list all the contributors

Description

On the occasion of Hacktoberfest and to help beginners who have just started to get there hands dirty with GIt and Github, this repository is to guide newcomers and open source enthusiasts to come together and contribute.
The first issue is really simple, you only have to add the following fields in contributor.json file:

"<guthub_username>": {
   "country": "Your Country", // Required
   "name": "Your Name", // Required
   "linkedin": "linkedin URL", // Optional
   "twitter": "twitter URL", // Optional
   "website":"website or blog URL"//Optional
}

Here is a reference from an early contributor: #22

Steps

1. Fork the repository
2. Clone the repository you have forked (Appears in the repository section of your profile)
3. Checkout to a new branch. (Optional if you don't have a concept of branching)
4. Change in contributor.json add your information in the above json object. Note: Make sure you place your information in the correct order according to the GitHub user name in ascending order ignoring case sensivity. This is done to avoid many merge conflicts. If you don't want to do it manually, you can use the following command:

npx sort-json contributors.json --ignore-case

5. Commit the changes
6. Create a PR to the original repository
   Here's how to do it:
   Step 1: Go to Code section of forked repo an click on Pull request below the Code Button besides Compare Button
   Step 2: Make sure the following is branches are selected:

Here is a guide/lab if you haven't created any commits or PRs:
https://subeshbhandari.com/blog/git-and-github-practical-for-beginners

If you get stuck in any step feel free to tag me and request help

PS: Feel free to star the repository and follow me :)

After this, your PR will be reviewed and once all the checks pass it will be merged to master. The PR will we then labeled as hacktoberfest-approved

Outcome of this issue

• Collaboration and contribution to open source
• Experience continuous integration of code changes in a repository
• Be a part of Developer Community Stats

Repository Context

This repository shows the Github stats of every contributor that has contributed to the above file. In the future, more detailed stats will be shown for each individual contributor. For now, it only shows basic stats, for example, total contribution this year, followers, number of pull requests, repository count, etc. Once your PR gets merged it will be shown on the Website:
https://developer-community-stats.netlify.app/

Description

Add icons on the footer for the following technologies with their respective links:

1. React
2. Gatsby
3. Github
4. Graphql

Add a text Made with followed by icons.

Acceptance criteria

• The icons should be visible in both dark and light themes
• The layout should have proper design. (Explore some examples)

Description

When contributors contribute to contributors.json check for incorrect syntax and order of assignment

Acceptance criteria

• It should show a correct error message to a user on failure
• It should show a friendly message to a user on PR creation

Description

On the occasion of Hacktoberfest and to help beginners who have just started to get there hands dirty with GIt and Github, this repository is to guide newcomers and open source enthusiasts to come together and contribute.
The first issue is really simple, you only have to add the following fields in contributor.json file:

"<guthub_username>": {
   "country": "Your Country", // Required
   "name": "Your Name", // Required
   "linkedin": "linkedin URL", // Optional
   "twitter": "twitter URL", // Optional
   "website":"website or blog URL"//Optional
}

Here is a reference from an early contributor: #22

Steps

1. Fork the repository
2. Clone the repository you have forked (Appears in the repository section of your profile)
3. Checkout to a new branch. (Optional if you don't have a concept of branching)
4. Change in contributor.json add your information in the above json object. Note: Make sure you place your information in the correct order according to the GitHub user name in ascending order ignoring case sensivity. This is done to avoid many merge conflicts. If you don't want to do it manually, you can use the following command:

npx sort-json contributors.json --ignore-case

5. Commit the changes
6. Create a PR to the original repository
   Here's how to do it:
   Step 1: Go to Code section of forked repo an click on Pull request below the Code Button besides Compare Button
   Step 2: Make sure the following is branches are selected:

Here is a guide/lab if you haven't created any commits or PRs:
https://subeshbhandari.com/blog/git-and-github-practical-for-beginners

If you get stuck in any step feel free to tag me and request help

PS: Feel free to star the repository and follow me :)

After this, your PR will be reviewed and once all the checks pass it will be merged to master. The PR will we then labeled as hacktoberfest-approved

Outcome of this issue

• Collaboration and contribution to open source
• Experience continuous integration of code changes in a repository
• Be a part of Developer Community Stats

Repository Context

This repository shows the Github stats of every contributor that has contributed to the above file. In the future, more detailed stats will be shown for each individual contributor. For now, it only shows basic stats, for example, total contribution this year, followers, number of pull requests, repository count, etc. Once your PR gets merged it will be shown on the Website:
https://developer-community-stats.netlify.app/

Prerequisites ⚠️⚠️⚠️

You must have completed Issue #120

Description

This is a second challenge for Hacktoberfest. You will add a markdown file in directory readme-profiles named:

<github_username>.md

Add something about you and your showcases or projects. The information will be seen when you click on your stats on the home page.

Here is a reference for markdown https://github.com/subeshb1/developer-community-stats/blob/main/readme-profiles/subeshb1.md
You can also copy the content and simply replace the user's information with yours.

Steps

1. Fork the repository
2. Clone the repository you have forked (Appears in the repository section of your profile)
3. Checkout to a new branch. (Optional if you don't have a concept of branching)
4. Create a new file named <github_username>.md in readme-profiles directory.
5. Add some markdown with your information and show cases.
6. Commit the changes
7. Create a PR to the original repository
   Here's how to do it:
   Step 1: Go to Code section of forked repo an click on Pull request below the Code Button besides Compare Button
   Step 2: Make sure the following is branches are selected:

Here is a guide/lab if you haven't created any commits or PRs:
https://subeshbhandari.com/blog/git-and-github-practical-for-beginners

If you get stuck in any step feel free to tag me and request help

PS: Feel free to star the repository and follow me :)

After this, your PR will be reviewed and once all the checks pass it will be merged to master. The PR will we then labeled as hacktoberfest-approved

Outcome of this issue

• Collaboration and contribution to open source
• Experience continuous integration of code changes in a repository
• Learn about markdown
• Get more experience in creating Pull requests and reviews.

Output

Once your PR is merged you will see your profile by clicking on your card as below:

Description

Remove vertical scrollbar in Change website theme menu.

Description

Currently, the daily build cron is scheduled to run every 12 hours. Change it to run 4 hours.

Reference:

.github/workflows/main_deploy.yaml

Description

As the repository and number of contributor grows, it will be really good to see the growth in numbers. Create a page that shows the following statistics:

• Number of users per country
• Total number of contributors
• Highest contributors (Top 10) based on Pr and issues worked on
• graph showing number of contributors per day
• number of users joined per day

Description

New users are getting confused sorting their stats in contributors.json. It is cumbersome to do it manually. Create an action that sorts the file in ascending order and commits the file in the same pr.

Acceptance criteria

• Sort the file in ascending order if not.
• The spec should only be run after the commit and check id made.

Reference:

.github/workflows/contributor_spec.yaml

Description

When light primary color is set, the made with icons are not visible in footer:

Light Theme:

Dark Theme:

The icons must be visible in light theme as well.

Acceptance criteria

• The Made with icons should be visible in both light and dark primary colors

Description

Currently, only basic stats are shown on the home page. We want to show detailed stats of a user when clicked on the respective cards.

Acceptance criteria

• Create a separate page for each user
• Show detailed stats for each user

Description

If you have suggestions or feedback regarding the design of the website, repository structure please let me know in this issue. Any feedback would be highly appreciated. You can:

• suggest change,
• add your design,
• or simply comment on your thoughts,
• and share what you've learned

Prerequisites

You must have completed Issue #68

Description

This is a second challenge for Hacktoberfest. You will add a markdown file in directory readme-profiles named:

<github_username>.md

Add something about you and your showcases or projects. The information will be seen when you click on your stats on the home page.

Here is a reference for markdown https://github.com/subeshb1/developer-community-stats/blob/main/readme-profiles/subeshb1.md
You can also copy the content and simply replace the user's information with yours.

Steps

1. Fork the repository
2. Clone the repository you have forked (Appears in the repository section of your profile)
3. Checkout to a new branch. (Optional if you don't have a concept of branching)
4. Create a new file named <github_username>.md in readme-profiles directory.
5. Add some markdown with your information and show cases.
6. Commit the changes
7. Create a PR to the original repository
   Here's how to do it:
   Step 1: Go to Code section of forked repo an click on Pull request below the Code Button besides Compare Button
   Step 2: Make sure the following is branches are selected:

Here is a guide/lab if you haven't created any commits or PRs:
https://subeshbhandari.com/blog/git-and-github-practical-for-beginners

If you get stuck in any step feel free to tag me and request help

PS: Feel free to star the repository and follow me :)

After this, your PR will be reviewed and once all the checks pass it will be merged to master. The PR will we then labeled as hacktoberfest-approved

Outcome of this issue

• Collaboration and contribution to open source
• Experience continuous integration of code changes in a repository
• Learn about markdown
• Get more experience in creating Pull requests and reviews.

Output

Once your PR is merged you will see your profile by clicking on your card as below:

Description

When light primary color is set, the made with icons are not visible in footer:

Light Theme:

Dark Theme:

The icons must be visible in light theme as well.

Acceptance criteria

• The Made with icons should be visible in both light and dark primary colors

Description

The footer layout for mobile has broken text alignment:

TheMade With text and copyright text overlap each other. We need to fix the alignment.

Acceptance criteria

• Make sure the text doesn't align in mobile layout
• Ensure the copyright text goes below the Made with content

Description

This is a revision to #231, where filters and sorters were added. However, it used a package ant-design that broke all the websites UI and imported unnecessary CSS. We had to revert the changes. Currently, there are sorters that when clicked sorts the lists accordingly.

We need to add the following filters:

1. Github user name
2. Country
3. User name

The design is open for suggestions.

Acceptance criteria

• Filters must be responsive and easy to use
• If external packages are used, they must not alter the site's styles
• Screenshot and GIF in the PR

Description

After the introduction of the ant-d package to add filters, the existing interface design has broken.

Examples:

Before

Present

There seems to be unnecessary padding, margin, and fonts that have been overridden.
We need to make importing ant-d doesn't break other UI interfaces.

Acceptance criteria

• Make sure the UI is not broken by ant-d css

Description

Add a GitHub action to put emoji whenever a new pull request is opened from a forked repository.

Description

In dark mode, the sort buttons are not visible.

Make sure that the buttons are visible in both dark and light theme

Acceptance criteria

• Make sure the buttons are visible in both dark and light theme
• Screenshot of changes in PR

Description

The user search input is not responsive in mobile devices

Make sure that the input is responsive in mobile devices

Acceptance criteria

• Make sure that the input is responsive in mobile devices
• Screenshot of changes in PR

Description

Currently, when the developer card is hovered over by a mouse, it shows a link to go to the profile page. We had a suggestion to add smooth transitions to it.

Acceptance criteria

• Make a smooth transition to show a link to go to profile page when Developer card is hovered. (Feel free to use your creativity)
• The theme changes color should apply as well
• Add a GIF to show the changes

Description

A lot of beginners don't read the descriptions and don't check to see if the order is in ascending or not. Create a GitHub action step in spec action to add a comment of spec fails. List the steps to do it.

Description

To help beginners who have just started to get their hands dirty with GIt and Github, this repository is to guide newcomers and open source enthusiasts to come together and contribute.
The first issue is really simple, you only have to add the following fields in contributor.json file:

⚠️ ⚠️ ⚠️ Add the values in ascending order alphabetically by Github user name ⚠️ ⚠️ ⚠️

"github_username": {
   "country": "Your Country", // Required
   "name": "Your Name", // Required
   "linkedin": "linkedin URL", // Optional
   "twitter": "twitter URL", // Optional
   "website":"website or blog URL"//Optional
}

Here is a reference from an early contributor: #22

Steps

1. Fork the repository
2. Clone the repository you have forked (Appears in the repository section of your profile)
3. Checkout to a new branch. (Optional if you don't have a concept of branching)
4. Change in contributor.json add your information in the above JSON object. Note: Make sure you place your information in the correct order according to the GitHub user name in ascending order ignoring case sensitivity. This is done to avoid many merge conflicts. If you don't want to do it manually, you can use the following command:

npx sort-json contributors.json --ignore-case

5. Commit the changes
6. Create a PR to the original repository
   Here's how to do it:
   Step 1: Go to Code section of forked repo an click on Pull request below the Code Button besides Compare Button
   Step 2: Make sure the following is branches are selected:

Here is a guide/lab if you haven't created any commits or PRs:
https://subeshbhandari.com/blog/git-and-github-practical-for-beginners

If you get stuck in any step feel free to tag me and request help

PS: Feel free to star the repository and follow me :)

Outcome of this issue

• Collaboration and contribution to open source
• Experience continuous integration of code changes in a repository
• Be a part of Developer Community Stats

Repository Context

This repository shows the Github stats of every contributor that has contributed to the above file. In the future, more detailed stats will be shown for each individual contributor. For now, it only shows basic stats, for example, the total contribution this year, followers, number of pull requests, repository count, etc. Once your PR gets merged it will be shown on the Website:
https://developer-community-stats.netlify.app/