Self-paced

Explore our extensive collection of courses designed to help you master various subjects and skills. Whether you're a beginner or an advanced learner, there's something here for everyone.

Bootcamp

Learn live

Join us for our free workshops, webinars, and other events to learn more about our programs and get started on your journey to becoming a developer.

Upcoming live events

Learning library

For all the self-taught geeks out there, here is our content library with most of the learning materials we have produced throughout the years.

It makes sense to start learning by reading and watching videos about fundamentals and how things work.

Full-Stack Software Developer - 16w

Data Science and Machine Learning - 16 wks

Search from all Lessons

LoginGet Started
← Back to Lessons

Weekly Coding Challenge

Every week, we pick a real-life project to build your portfolio and get ready for a job. All projects are built with ChatGPT as co-pilot!

Start the Challenge

Podcast: Code Sets You Free

A tech-culture podcast where you learn to fight the enemies that blocks your way to become a successful professional in tech.

Listen the podcast
Edit on Github

Confirm Categorize And Clean Stale Bugs

Watch these Videos:
Procedure:

Watch these Videos:

  • Understanding Stale Issues in GitHub
  • Daily Task: Checking Unassigned Issues

Procedure:

  1. Enter GitHub:

    • Navigate to the GitHub repository and search for stale bug reports or unassigned issues.
    • You can find them using this link or by applying the filters: is:issue label:stale no:assignee is:open.

  2. Read and Understand:

    • Read the bug reports to understand the type of bug and where it is occurring.

  3. Replicate or Confirm:

    • Try to replicate the error mentioned in the report.
    • Visit the website mentioned in the report to confirm if the bug is still present.

  4. Action Based on Confirmation:

    • If the bug is still present:
      • Remove the stale label.
      • Add one or more of the following labels:
        • Confirm: If it was confirmed that the bug is still occurring.
        • BUG: If it is indeed a mistake.
        • Front end: If the bug is a frontend bug.
        • Back end: If the bug is a backend bug.
    • If you can't confirm the bug:
      • Add the label ✋ waiting-for-feedback.
      • Review it in the standup meeting.
    • If the bug is not happening:
      • Close the issue by adding a comment.

Following this procedure will help streamline the bug reporting and management process, ensuring that issues are properly identified, confirmed, and addressed in a timely manner.