Find a bug in what works. Finding a bug in a non-existent feature is invalid.
Issue #7 is basically asking you to find out a bug in this project by heavily testing it (manually, coz I've not yet added any automated tests).
Once done, in the PR commits, you just need to create a docs/<your_username>/bug_<title>.md file with info on the bug. Also copy paste the info into a new issue (create a new issue coz it really helps).
Details of the bug
The bug should be reproducible.
The bug report should contain every step required to reproduce the bug.
If required, a link to a repo having code or project that triggers the bug should be given.
Stack traces help a lot, so if the framework produces one, or some logs, that should be included in the report.
You should report any bug, including but not limited to UI/UX, logic, security, and bad function usages.
Updating code
If you modify or add code, it may go through a stricter review.
Use in HacktoberFest
In return (on your PR submission) you get a HacktoberFest 2023 contribution.
All non-spam and well-written PRs will get labelled hacktoberfest-accepted, even if they're not merged.
Details
Find a bug in what works. Finding a bug in a non-existent feature is invalid.
Issue #7 is basically asking you to find out a bug in this project by heavily testing it (manually, coz I've not yet added any automated tests).
Once done, in the PR commits, you just need to create a
docs/<your_username>/bug_<title>.md
file with info on the bug. Also copy paste the info into a new issue (create a new issue coz it really helps).Details of the bug
Updating code
If you modify or add code, it may go through a stricter review.
Use in HacktoberFest
In return (on your PR submission) you get a
HacktoberFest 2023
contribution.All non-spam and well-written PRs will get labelled
hacktoberfest-accepted
, even if they're not merged.PS
Someone will fix the bug someday.