Issue and PR?

[rajvaidyanath27]

Got confused between like should i raise any issue or just fork a repo start contributing to it?? or wait for the admin to assign us the issue

[Ojas-Arora]

It's common to feel confused about whether to raise an issue or start contributing directly to a project, especially as a newcomer to open source. Here's a breakdown to help you understand when to do each:

Raising an Issue:

1. When to do it:

   • You've found a bug or an improvement idea in the project.
   • You want to suggest a new feature.
   • You need clarification or guidance on something related to the project.

2. How to do it:

   • Navigate to the project's issue tracker on GitHub.
   • Click on "New Issue."
   • Provide a clear title and description of the issue or feature request.
   • Use appropriate labels (if available), like "bug," "enhancement," or "help wanted."

Forking and Contributing:

1. When to do it:

   • You find an existing issue in the project's issue tracker that you want to work on.
   • You've identified something to contribute that doesn't have an issue associated with it (like documentation improvements, code refactoring, etc.).

2. How to do it:

   • Fork the project's repository on GitHub.
   • Clone your forked repository to your local machine.
   • Create a new branch for your changes (git checkout -b <branch-name>).
   • Make your changes and commit them.
   • Push your changes to your forked repository (git push origin <branch-name>).
   • Create a pull request from your branch to the original project's repository.

Wait for Admin to Assign:

• Some projects may have a workflow where they prefer to assign issues to contributors, especially if they're larger or more complex tasks. In this case, it's okay to wait for the admin to assign you an issue if you prefer to work on a specific task rather than choosing one yourself.

Tips:

• If you're not sure whether to raise an issue or start contributing directly, consider reaching out to the project maintainers or community members for guidance.
• It's usually a good idea to start with smaller tasks (like those labeled as "good first issue" or "beginner-friendly") if you're new to contributing to open source. This helps you get familiar with the project's workflow and codebase.

Remember, the ultimate goal is to contribute meaningfully to the project, whether it's by raising issues, working on assigned tasks, or contributing directly. Choose the approach that feels most comfortable for you and aligns with the project's guidelines and your own learning objectives.

[SpaciousCoder78]

Stop over-using ChatGPT. Give your own answers or refrain from answering. If you don't have anything to answer, just refrain from answering but don't dump those generic ChatGPT answers here.

[sanjay-kv]

@Ojas-Arora I see lot of Chat gpt use, people here to get relevant information regarding the girlscript, so make sure you type it, else I may have to block and loose all badges. @SpaciousCoder78 I have taken this into consideration.

[Ojas-Arora]

ok sir I will take of it from now onwards and sorry for that

[aswinikalyan30]

Wait for assignment of the issue - fork the repo - make the changes and raise PR - get it reviewed by mentors/Project admin - merge it

[iHRex]

Hello @rajvaidyanath27

1. Create an issue(If not already exist)
2. Let the Project Admin(PA) know, you want to fix the issue.
3. Wait for the Project Admin to assign you the issue.
4. Start working on the assigned issue.
5. On completion, raise a pull request(PR).
6. If any error, or correction required - FIX IT
7. Else, wait for the pull request to get merged,
8. Hurry! You've earned you point.

In Open Source, we use PR as an abbreviation for PULL REQUEST. I'd request you to kindly go through the sample video: https://www.youtube.com/watch?v=rgbCcBNZcdQ

Hope it helps

[paridhi1509]

hi @rajvaidyanath27
Only create an issue if it doesn't exist already otherwise just browse through the existing issues and if you find one which you would like to work on then comment on it asking to be assigned and wait for the Project Admin to assign the issue and then start working on it.
Working on that before getting assigned might lead to your solution not getting recognised. As soon as you have finished working on the project then raise a PR and wait for it to get merged.

[Kashif581]

Hi @rajvaidyanath27
If you find an issue then create the issue, otherwise if you browse through the existing issues and if you find one you like to work one then ask for assignment then don't wait for the admin to assign you, just start working on it and once you solve that issue make a pull request.

[SpaciousCoder78]

If I were you, I would raise an issue, get the issue assigned to me and then start the work on the issue and submit a PR because Your contributions will only count towards GSSoC if the issue you worked on is assigned to you because each issue has its level 1-3 which gets you the contribution points for GSSoC

[TonyStark-47]

It's upto you. Just start experimenting.