Challenge #4 - Nikunj

[navdiya-nikunj]

name: Nikunj Navdiya github_user_name: navdiya-nikunj discord_id: nikunjnavdiya

[navdiya-nikunj]

URL of your forked repository

[navdiya-nikunj]

[navdiya-nikunj]

[navdiya-nikunj]

[navdiya-nikunj]

[navdiya-nikunj]

Challange #10

[navdiya-nikunj]

Challenge 11

[navdiya-nikunj]

challenge 15

[navdiya-nikunj]

Challange 16

[navdiya-nikunj]

Challenge 17

[navdiya-nikunj]

challenge 18

[navdiya-nikunj]

Challenge 19:

my experience with github codespace

I enjoyed working with GitHub Codespaces during this challenge. The interface is clean and intuitive, making it easy to get started with a ready-to-code dev environment in the cloud.

Some of the features I found most useful were:

• Instant cloud dev environment - Being able to spin up a dev environment in seconds without needing to configure anything locally was extremely convenient.

• Integrated GitHub - Having my code repository and Codespace environment closely connected made for a streamlined workflow. I could easily push code changes, raise PRs, etc.

• Built-in Terminal - The terminal access allowed me to run commands, install additional tools, and work like I would locally. Fast launch times - Codespaces loaded very quickly each time I launched them, even for larger projects.

The main challenge I ran into was around configuring the Codespaces environment itself. While the default setup works well, I found customizing the environment like adding additional tools or dotfiles to be tricky. The configuration options aren't yet as flexible compared to manually setting up a dev container.

Going forward, I can see myself using Codespaces for:

• Quickly testing out new projects or repositories without worrying about local setup

• Onboarding onto new teams or repositories with minimal local configuration

• Developing while traveling or when I don't have access to my usual machine

Overall, the experience was smooth and I'm excited to use Codespaces more in my daily workflow. The convenience of cloud dev environments combined with GitHub integration makes Codespaces very compelling.

[navdiya-nikunj]

Challange 20

Experience with github actions

Setting up GitHub Actions workflows for code linting was a great learning experience for me. Since this was my first time setting up linting in GitHub Actions, it took me some trial and error to get it right.

I started by reading GitHub's documentation on how to set up a linting workflow. The documentation provided a good template that I could customize for my specific linting tools and code language.

It took me a few attempts to get the YAML syntax right for defining the linting job. I encountered some errors like incorrect indentations and unresolved references during my early attempts. Getting the workflow script validated on the YAML parser before committing it helped me identify these syntax issues.

Configuring the workflow to install the linting dependencies and run the lint command on my code was straightforward to set up. I appreciate how reusable Actions like the GitHub Super-Linter make this easy.

Seeing the linting results directly in the pull request feedback through annotations was really useful. This saves me time by catching issues early without needing to run linting locally.

Debugging some initial linting errors that popped up in my code was a good learning experience. The workflow errors pointed me to the exact files and line numbers to fix.

Overall, setting up GitHub Actions for linting taught me how automating quality checks on code can fit right into my development workflow. I'm excited to expand on this by setting up more workflows for test coverage, security, etc.

[navdiya-nikunj]

Challenge 21

[navdiya-nikunj]

Challenge 22:

[navdiya-nikunj]

Challange 24:

Summary for opensource contribution

Here is a summary of key learnings from the resources provided on best practices for open source contribution, especially around issue creation, branch naming and pull requests:

• For issue creation, be clear and concise with the title and description. Provide steps to reproduce the bug or detailed explanation of the desired feature request. Use labels and milestones to categorize.

• For branch naming, use short descriptive names with slashes to separate words like feature/new-modal. Avoid generic names like dev or temp. Delete merged branches to keep clean.

• For pull requests, use clear title summarizing change. Provide detailed description of changes, reason for change, and anything the reviewer needs to know. Link related issues. Follow style guides. Keep changes small and focused. Request review from specific people. Mark WIP and draft PRs clearly.

• In general, provide context through communicate. Follow community guidelines and conventions. Make focused, incremental changes. Stay up to date with main/master branch. Be responsive to feedback. Avoid force pushes when possible. Adopt a "voice" similar to project.

• Comment code clearly, write tests, squash before merging, handle rebase/conflicts proactively, review others' PRs, get involved in discussion. Focus on being helpful and improving project.

[navdiya-nikunj]

Challange 25

day 1 of actual contribution

Yesterday was a productive day as I delved into the GitHub Explore section to explore topics that piqued my interest. It was an exciting journey through a vast repository of open-source projects and communities, where innovation knows no bounds.

As I navigated through the diverse topics, I stumbled upon some intriguing repositories that aligned perfectly with my interests. It was like uncovering hidden gems in the world of coding and development. These repositories held the promise of learning and contributing to something meaningful.

One of the highlights of my exploration was discovering "good first issue" tags on various repositories. These issues seemed like excellent entry points for someone looking to contribute to open-source projects. It was heartening to see how the open-source community welcomes newcomers and offers opportunities for collaboration and growth.

With the GitHub Explore section as my guide, I embarked on a journey of curiosity, discovery, and potential collaboration. It was a reminder of the power of the open-source community, where individuals from around the world come together to build, share, and innovate.

In the coming days, I look forward to rolling up my sleeves and getting involved in these exciting projects. GitHub has once again proven to be an invaluable resource for developers and enthusiasts like me, offering endless opportunities to learn, grow, and make a positive impact on the world of technology.

[navdiya-nikunj]

Challange 26:

Day 2

Today i explored the python topic in github explore and checked all issues in it to see in which i can contribute.

[navdiya-nikunj]

Challange 27

[navdiya-nikunj]

Challange 28

Day 3

• Learnt git advance search and found interested projects.

• Explore some code bases of web3 projects