search

scaleracademy / scaler-open-source-september-challenge

335 stars 456 forks source link

Challenge #1 - Ayan Saxena #183

Open Ayansaxena24 opened 1 year ago

Ayansaxena24 commented 1 year ago

name: Ayan Saxena github_user_name: Ayansaxena24 discord_id: ayansaxena24

Ayansaxena24 commented 1 year ago

TASK 2 : URL of Forked Repository - https://github.com/Ayansaxena24/scaler-open-source-september-challenge Screenshot of Cloned Repo in my system : task 2

Ayansaxena24 commented 1 year ago

Task - 3

Screenshot of list of all branches in the forked repository.

task 3 - 2

Ayansaxena24 commented 1 year ago

Task - 4

Screenshot showing the latest repository contents of my forked clone repository locally:

Task 4 Task 4 - 2

Ayansaxena24 commented 1 year ago

Task 5 : Completed

Task 5

Ayansaxena24 commented 1 year ago

TASK 6 : Completed

Task 6 2

Task 6 git bash

Ayansaxena24 commented 1 year ago

Task 7 - Completed

Task 7 Git Task 7 Git 2 Task 7 issue

Ayansaxena24 commented 1 year ago

Task 8 - Completed

Task 8 Task 8 2

Ayansaxena24 commented 1 year ago

Task 9 -> Completed

Task 9 Task 9 2

Ayansaxena24 commented 1 year ago

Task 10 --> Completed

task 10 - 3

task 10

task 10 - 2

Ayansaxena24 commented 1 year ago

Task 11 --> Completed

Task 11

Ayansaxena24 commented 1 year ago

Task 12 --> completed

task 12 - 3

Task 12

task 12 - 2

Ayansaxena24 commented 1 year ago

Task 13 --> Completed

task 13 github

Task 13 Gists

Task 13

Ayansaxena24 commented 1 year ago

Task 14 --> completed

Task 14

Task 14 code 1

Task 14 code 2

Task 14 code 3

Ayansaxena24 commented 1 year ago

Task 15 --> Completed

Task 15

Ayansaxena24 commented 1 year ago

Task 16 --> Completed

Task 16

Task 16 2

Ayansaxena24 commented 1 year ago

Task 17 --> Completed

Task 17

Ayansaxena24 commented 1 year ago

Task 18 --> Completed

Challenge 18

Ayansaxena24 commented 1 year ago

Task 19 --> Completed

One of the amazing features of Github Codespaces is live working tree.

Task 19

Task 19 2

Ayansaxena24 commented 1 year ago

Task 20 --> Completed

Task 20

Task 20 - 2

Ayansaxena24 commented 1 year ago

Task 21 --> Completed

TASK 21

Ayansaxena24 commented 1 year ago

Task 22 --> Completed

Challenge 22

Ayansaxena24 commented 1 year ago

Task 23 --> Completed

Task 23

Task 23 2

Ayansaxena24 commented 1 year ago

Task 24 --> Completed

Summary of all the Information :

This collection of articles and guidelines revolves around best practices for Git branching and creating effective pull requests (PRs). Here's a summary of the key points from each section:

Git Branching Naming Convention: Best Practices:

Git branching strategies help teams manage their code repositories effectively. There are two main categories of branches: Regular (permanent) and Temporary (created and deleted as needed). Best practices for branch naming: Start branch names with a clear group word (e.g., "Bug" or "WIP"). Use unique IDs, such as issue tracker IDs, in branch names for tracking and progress monitoring. Choose hyphens, slashes, or underscores as separators and be consistent. Consider including the author's name in branch names for better tracking. Avoid using numbers only as branch names, as they lack context. Maintain consistency in naming conventions within your team. For long-lived branches, keep names concise and informative. Building a Great Pull Request:

A well-crafted pull request (PR) is vital for efficient collaboration. Tips for creating effective PRs: Give your feature branch a clear name, potentially including initials or a group word. Use active and descriptive titles for commits and PRs, employing the present imperative tense. Streamline the PR creation process using tools and scripts. Provide a meaningful PR description, explaining the "Why," "How," and "What" of your changes. Visualize your changes using images or GIFs whenever possible. Review your own PR before assigning it to others, addressing conflicts, running tests, and ensuring code quality. Finding an Issue:

To contribute to open-source projects effectively, you should start by identifying suitable issues. Different labels on GitHub issues indicate their status and whether they are open for community contribution. Use GitHub's Issue Finder tool and saved searches to discover appropriate issues. Always check for existing work on an issue before starting to avoid duplication. The contribution process involves claiming an issue, writing code, submitting a pull request, and engaging in code reviews. Collaboration and reviewing other contributors' PRs is encouraged. Proposing a New Issue:

If there's no existing issue for your proposed change, you should create one. Include detailed information about your proposed change and its implementation in the new issue. Most projects prefer new changes to be proposed through issues before creating pull requests. Wait for project maintainers to evaluate your proposal before starting work.

In summary, these articles provide insights into Git branching strategies, best practices for creating pull requests, finding and proposing new issues, and the importance of consistent naming conventions. These practices help streamline collaboration and code management in software development projects.

Ayansaxena24 commented 1 year ago

Task 25 --> Completed

I have made a pull request in an open source Repo. The Pull Request Link is --> https://github.com/minhaj-313/Portfolio-1/pull/98

Ayansaxena24 commented 1 year ago

Task 26 --> Completed

Pull Request Link --> https://github.com/minhaj-313/Portfolio-1/pull/98

Ayansaxena24 commented 1 year ago

Task 27 --> Completed

Task 27 0

Task 27

Ayansaxena24 commented 1 year ago

Task 28 --> Completed

Pull Request Link --> https://github.com/minhaj-313/Portfolio-1/pull/98

Ayansaxena24 commented 1 year ago

Task 29 --> Completed

github com_Ayansaxena24