I am very excited to be participating in my first Hacktoberfest!

I am a bit late to the party, but for my first Pull Request, I wanted to find something simple to get used to the process and to make sure my PR gets accepted.

Here are some methods I used to look for my first issue, if you find it helpful do use them as well!

• Looked through GitHub Issues with labels "Hacktoberfest" and "good first issue", and 0 comments
• Looked through Hacktoberfest labelled repos with simple installation instructions and easy to understand instructions. Cloned the apps on my local and tested them to check for bugs or enhancements.
• Looked through the Hacktoberfest Discord #project-sharing channel where people share their projects and clicked on ones I found interesting, and either checked the Issues list or tested the app myself.

TIP! When you find an issue you would like to work on, leave a comment immediately to ask the owner to assign you the issue. Then, if the issue is a simple one, do the fix and submit a PR linking it to the issue as soon as possible. I discovered that many times that although I commented first, that others would go ahead and submit PRs for that issue anyways.

After some exploration, I found the following issue which I believe to be a suitable first PR

[FIX]: Correct the links to sample files in README.md #3

mohiwalla posted on Oct 13, 2023

After changing the file names in Samples/ folder the links in README.md file are now not in working condition and getting a 404 Error due to that. So, fix the links in README.md file.

Happy Hacking

View on GitHub

The issue is a very straightforward README file fix. The owner has renamed four files, and thus the links to those four files under the "Server-Side File" section of the README stopped working. I did not have to do much setup to do this fix.

I commented under the issue that I would like to work on the issue. I forked the repo and then cloned the forked repo to my local. I created a branch and called it issue-3. I located the files inside the Samples folder and I updated the file names for those four files in the README.md. I then pushed my changes to my branch, and then manually went to my branch on GitHub to test that all four links now work. Lastly, I created a Pull Request, detailed my fix and my testing, and linked it to the issue.

I am very happy to have completed my first Pull Request, and I look forward to getting a review from the owner. I have already communicated with the owners of other repos and have gotten assigned to a couple of more difficult tasks, and I look forward to working on them in the coming days and weeks!

UPDATE: Unfortunately, even though I asked to be assigned to this issue first, someone submitted a PR a couple minutes before me, and so my PR was not merged.