Issues test and explination

What is the GitHub "Issues" Tab?

The Issues tab is a built-in project management and tracking tool inside a GitHub repository. Think of it as a digital to-do list and discussion forum. Instead of emailing or writing messy reminders, I will use Issues to track everything that needs fixing, changing, or discussing in a project. I will make sure Issues are posted and if any one is working on a particular problem that isn't listed please do so, as this informs the group what is currently being worked on.

Creating a New Issue

1. Navigate to the main page of your GitHub repository.
2. Click the Issues tab (located right next to the "Code" tab).
3. Click the green New Issue button.Enter a Title (e.g., Fix broken login button on mobile view).
4. Write a Description explaining the problem, how to reproduce it, or what needs to be built.
5. Click Submit new issue.

Organizing and Categorizing (The Sidebar)

On the right-hand side of any open issue, you will see meta-options to organize the task:

• Assignees: Assign the task to yourself or a teammate so everyone knows who is responsible for it.
• Labels: Color-coded tags to sort issues. Common defaults include bug (something is broken), enhancement (new feature request), and good first issue (great for beginners).
• Milestones: Group related issues into a larger goal or deadline (e.g., Launch Version 1.0).

Discussing and Collaborating

• Anyone with access to the repository can leave a comment at the bottom of the issue.
• You can use Markdown to add code snippets, checklists (- [ ] task), images, or bullet points.
• Mention other contributors using their username (e.g., @username) to send them a notification.

Closing the Issue

• Once the bug is fixed or the feature is built, type a final comment detailing the solution.
• Click Close issue to move it off the active to-do list.

Pro-Tip: Connecting Issues to Your Code

-You can automatically close an issue by linking it to a code change (a Pull Request). If you type Fixes #12 (where 12 is the issue number) in your Pull Request description, GitHub will automatically close Issue #12 the exact moment your code is merged into the project.