From 1a16dbde4f6e9dbdc6b10b0e41915a11d915eb1a Mon Sep 17 00:00:00 2001 From: "Abhiraj Roy (iconized)" <157954129+iconized@users.noreply.github.com> Date: Tue, 16 Apr 2024 01:40:32 +0530 Subject: [PATCH] update bur report url > https://github.com/Snigdha-OS/snigdhaos-issues/issues --- docs/introduction/reporting_bugs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/introduction/reporting_bugs.md b/docs/introduction/reporting_bugs.md index 2143e0d0..bab7a9ad 100644 --- a/docs/introduction/reporting_bugs.md +++ b/docs/introduction/reporting_bugs.md @@ -17,7 +17,7 @@ Thank you for helping us test Snigdha OS. We're happy to have you on the team! W Found a bug already? Wonderful! We'd love to hear about it — but first you should check around to make sure you're not wasting your time on a known issue: - Search our [Support forum](https://forum.snigdhaos.org/t/support) to see if it's already been reported. -- We could be working on a fix, so search our [issue tracker](https://github.com/Snigdha-OS/snigdhaos-arctic/issues) too. +- We could be working on a fix, so search our [issue tracker](https://github.com/Snigdha-OS/snigdhaos-issues/issues) too. If you've searched *thoroughly* and come up empty-handed, we'll welcome your report. If it's just a simple issue (a misspelled word or graphics glitch, for example) skip to the next paragraph. But if you're seeing errors, or something is clearly broken, we'll need you to gather some information first. Please head over to our [Troubleshooting](/category/troubleshoot) guide and follow the instructions there. Collect as much info as you can! @@ -29,4 +29,4 @@ If you can, check if the issue is reproducible with the latest version of Snigdh Remember: the goal of a bug report is to make it easy for us to replicate the bug and fix it. You might want to read [this article](/blog/effective_bug_report) for some useful tips on how to write an effective bug report. It is **required** that you clearly describe the steps necessary to reproduce the issue you are running into. Issues with no clear reproduction steps will not be triaged. If an issue labeled "needs verification" receives no further input from the issue author for more than 5 days, it will be closed. -> Once you've posted your report, we'd ask that you please *follow the discussion* and wait patiently. We may need to ask for further details or clarification; but we've always got plenty to do, and it could be a while before we can give your report the time it deserves. \ No newline at end of file +> Once you've posted your report, we'd ask that you please *follow the discussion* and wait patiently. We may need to ask for further details or clarification; but we've always got plenty to do, and it could be a while before we can give your report the time it deserves.