Challenge-akshat-mishra

[akshatmishra25]

name: Akshat Mishra github_user_name: akshatmishra25 discord_id: Akshat25_coder#1830

[akshatmishra25]

Day 2 Repo Link - https://github.com/akshatmishra25/scaler-open-source-september-challenge Screenshot of cloned repo -

[akshatmishra25]

Day 3:

[akshatmishra25]

Day 4

[akshatmishra25]

Day 5:

[akshatmishra25]

Day 6:

[akshatmishra25]

Day 7:

[akshatmishra25]

Day 8:

[akshatmishra25]

Day 9:

[akshatmishra25]

Day 10:

[akshatmishra25]

Day 11:

[akshatmishra25]

Day 12:

[akshatmishra25]

Day 13:

[akshatmishra25]

Day 14:

[akshatmishra25]

Day 15:

[omkarkhambekar]

Day15 challenge completed on merge conflict and how to resolve those manually.

[akshatmishra25]

Day 16:

[akshatmishra25]

Day 17:

[akshatmishra25]

Day 18:

[akshatmishra25]

Day 19:

I really loved Github Codespaces as it made my workflow more productive. It can help me make big and small changes directly from my browser and not depend on my local system. It can help me collaborate with various developers on real-world projects seamlessly and hassle-free. Really looking forward to more such tasks with Codespaces.

[akshatmishra25]

Day 20: I always wanted to learn Github Actions as by reading it felt such a fascinating term. But I never really used it before. Thanks to Scaler I was able to take my ambitions into reality. Github Actions seems to me as an amazing feature to maintain my codebase and workflow runs. Expecting to learn more.

[akshatmishra25]

Day 21:

[akshatmishra25]

Day 22: Screenshot for making Alias -

Screenshot for using alias-

[akshatmishra25]

Day 23:

[akshatmishra25]

Day 24: Git Branching Naming Convention: Best Practices:

This article discusses Git branch naming conventions, distinguishing between regular and temporary branches. It offers best practices for branch names, such as starting with a group word, using unique IDs, and avoiding long, descriptive names for long-lived branches.

Building a Great Pull Request:

This article provides practical tips for creating effective pull requests (PRs), including giving clear branch names, using descriptive commit and PR titles, streamlining the PR process, adding meaningful descriptions, using visuals, and self-reviewing PRs.

Contribution Guidelines from opensource.creativecommons.org:

These guidelines focus on finding and proposing issues for open source projects. They categorize issues, emphasizing the importance of creating a GitHub issue before starting work on a proposed change. Project maintainers review and approve issues before code contributions begin.

[akshatmishra25]

Day 25: Today I tried to go through a tool/tech that is quite a hot topic of discussion in the tech community, Bun.js. Went through many open good first issues in Bun.js - https://github.com/oven-sh/bun/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22+no%3Aassignee

Well, I was already researching about Bun for few days so I once commented on one of Bun's issues a while back. Today I took the liberty of contributing again by providing the exact documentation update I'm willing to work upon. Let's hope that it gets viewed by someone from the community. The link to the comment- https://github.com/oven-sh/bun/issues/5114#issuecomment-1734394332

[akshatmishra25]

Day 26: Got no updates from Bun.js. So searched for more open issues here and there. Found the following issues which was not worked upon till now. https://github.com/wikimedia/mediawiki-api-demos/issues/233 Commented on the issue. Hope that the issue gets assigned to me.

[akshatmishra25]

Day 27:

[akshatmishra25]

Day 28: Still got no updates from Bun.js. I will look out into more open issues in other organizations as currently I'm not getting any updates from the repos I was already looking into.

[akshatmishra25]

Day 29: Created my profile README, looks fantastic https://github.com/akshatmishra25