Skip to main content

Python print() Function

When you start learning Python, one of the first things you need to learn is how to display information on the screen. For example, you might want to display: A welcome message. Your name and age. The result of a mathematical calculation. Student marks and results. Information generated by a Python program. Python provides a built-in function called print() for displaying information. The print() function is one of the simplest and most frequently used functions in Python. It helps programmers display information while testing programs, solving problems, and developing applications. In this article, we will learn how to use print() with practical examples and their outputs. 1. What Is the print() Function in Python? The print() function is a built-in Python function that displays information in the output area, usually the terminal or console. Let's look at a simple example. print("Hello, World!") Output: Hello, World! In this example, Python displays the text Hello,...
Post a Comment

GitHub Labels Explained: How to Organize Issues, Bugs & Features Like a Pro

If you've ever explored a large GitHub repository, you may have noticed colorful tags such as bug, enhancement, documentation, help wanted, or good first issue next to Issues and Pull Requests.

These tags are called GitHub Labels.

Labels are a simple but powerful way to organize work inside a GitHub repository. They help developers quickly understand what an Issue is about, how important it is, and what type of work needs to be done.

In this article, you'll learn what GitHub Labels are, how they work, how to create them, how to use them with Issues and Pull Requests, and how they can make a GitHub project easier to manage.

What Are GitHub Labels?

A GitHub Label is a colored tag that can be attached to an Issue or Pull Request.

For example:

🐛 bug
✨ enhancement
📚 documentation
🔥 high priority
🟢 good first issue

Labels provide information about the Issue or Pull Request without requiring someone to open it.

For example:

#25 Fix Login Button

🐛 bug
🔥 high priority

From these labels, you immediately know that the Issue is a bug and that it has high priority.

Why Are GitHub Labels Important?

Imagine a repository has 500 Issues.

Without labels, it can become difficult to identify:

  • Bugs

  • Feature requests

  • Documentation tasks

  • Beginner-friendly tasks

  • High-priority problems

  • Frontend work

  • Backend work

Labels allow developers to categorize these Issues.

Instead of looking through hundreds of Issues manually, you can filter them using labels.

GitHub Labels in Simple Words

Think of labels like stickers on files.

Suppose you have a folder containing:

100 documents

You could put stickers on them:

Important
Urgent
Personal
Work
Completed

Now you can quickly identify what each document is about.

GitHub Labels work in a similar way.

Common GitHub Labels

GitHub repositories commonly use labels such as:

LabelPurpose
bugSomething isn't working correctly
enhancementImprovement or new functionality
documentationDocumentation-related work
questionQuestion or clarification
help wantedMaintainers are looking for help
good first issueSuitable for beginners
duplicateAlready reported elsewhere
invalidIssue isn't considered valid
wontfixThe issue won't be addressed

Repositories don't have to use exactly these labels. Maintainers can create their own.

Bug Label

The bug label is used when something isn't working as expected.

Example:

🐛 Login button doesn't work on mobile

Label:
bug

This tells developers that the Issue requires investigation and potentially a fix.

Enhancement Label

An enhancement label usually indicates an improvement or new functionality.

Example:

✨ Add dark mode

Label:
enhancement

The existing application may already work correctly, but someone is suggesting an improvement.

Documentation Label

The documentation label is used for documentation-related work.

Examples:

Update installation instructions

Add API documentation

Fix README spelling mistakes

This helps separate documentation work from coding tasks.

Good First Issue

One of the most useful labels for beginners is:

good first issue

This label identifies tasks that may be suitable for people who are new to the project or open-source contribution.

For example:

🟢 Fix a spelling mistake in README

good first issue

Beginners can search for this label to discover potentially approachable contributions.

Help Wanted

The help wanted label indicates that project maintainers would appreciate contributions from the community.

For example:

Add documentation for the API

help wanted

This doesn't necessarily mean the task is beginner-friendly. It simply indicates that outside assistance is welcome.

Priority Labels

Some projects use labels to identify priority.

For example:

🔥 priority: high
🟡 priority: medium
⚪ priority: low

This helps developers decide which tasks should be handled first.

Technology-Based Labels

Labels can also identify which part of an application is affected.

For example:

frontend

backend

database

API

mobile

security

Suppose an Issue says:

API returns incorrect user data

It might receive:

bug
backend
API

Now developers can quickly understand the nature of the problem.

How to Create a GitHub Label

If you have the necessary repository permissions, you can create custom labels.

A typical process is:

  1. Open your repository.

  2. Go to Issues.

  3. Open the repository's label management area.

  4. Create a new label.

  5. Enter a name.

  6. Choose a color.

  7. Add a description if needed.

  8. Save the label.

Your new label can then be applied to relevant Issues and Pull Requests.

Applying a Label to an Issue

Suppose you have this Issue:

#42

Website crashes when submitting the form

You could assign:

🐛 bug

🔥 priority: high

frontend

Now anyone looking at the Issue can quickly understand it.

Applying Multiple Labels

An Issue can have multiple labels.

For example:

#58 Add Dark Mode

Labels:

enhancement
frontend
UI

This is useful because one Issue can belong to multiple categories.

Filtering Issues Using Labels

Labels become especially useful when a repository contains many Issues.

Suppose a repository has:

300 Issues

You only want to see bugs.

You can filter using:

bug

GitHub will show Issues associated with that label.

You could also filter for:

bug + high priority

to focus on important bugs.

Labels and Pull Requests

Labels aren't limited to Issues.

They can also be used with Pull Requests.

For example:

Pull Request #81

Add user authentication

Labels:

feature
backend
security

This allows maintainers to categorize Pull Requests as well.

Labels vs Milestones

Labels and milestones are different.

Labels

Used to categorize individual Issues or Pull Requests.

Example:

bug
frontend
high priority

Milestones

Used to group work toward a larger goal or release.

Example:

Version 2.0

A milestone might contain:

Issue #10
Issue #15
Issue #22
Pull Request #30

A simple way to remember:

Label → What is this?

Milestone → Which larger goal does this belong to?

Labels vs GitHub Projects

GitHub Projects organize and track work.

Labels categorize work.

For example:

GitHub Project
      ↓
Student Management System

Issue
      ↓
Fix login bug

Labels
      ↓
bug
backend
high priority

All three features can work together.

Example: Building a Website

Suppose you're developing a portfolio website.

You create these Issues:

#1 Create Homepage

#2 Fix Mobile Navigation

#3 Add Contact Form

#4 Update README

#5 Improve Website Speed

You can organize them using labels:

#1 Create Homepage
→ feature
→ frontend

#2 Fix Mobile Navigation
→ bug
→ frontend

#3 Add Contact Form
→ feature
→ frontend

#4 Update README
→ documentation

#5 Improve Website Speed
→ enhancement
→ performance

Now your repository is much easier to manage.

How Labels Help Open-Source Beginners

If you're new to open-source development, labels can help you find suitable contributions.

Look for labels such as:

good first issue

help wanted

documentation

beginner

You can then explore Issues that match your experience.

However, always read the Issue carefully before starting work.

A good first issue label doesn't guarantee that the task will be easy for everyone.

Best Practices for GitHub Labels

Keep Labels Simple

Don't create dozens of unnecessary labels.

Start with a small set that your project actually needs.

Use Consistent Names

For example, don't use:

High
High Priority
Urgent
Very Important

for the same concept.

Choose a consistent naming system.

Use Descriptions

A label description can explain when the label should be used.

For example:

bug

Something isn't working as expected.

This helps contributors apply labels consistently.

Use Colors Carefully

Colors can make labels easier to recognize.

For example:

bug → red-style color

documentation → blue-style color

enhancement → green-style color

The exact colors are up to the repository maintainers.

Common Beginner Mistakes

Using Too Many Labels

Too many labels can make a repository harder to understand rather than easier.

Creating Duplicate Labels

Avoid creating labels with nearly identical meanings.

Using Labels Inconsistently

If one developer uses bug and another uses error for the same type of problem, filtering becomes less useful.

Using Labels Without a Purpose

Every label should provide useful information.

Frequently Asked Questions

Can anyone create GitHub Labels?

Creating or managing repository labels generally requires the appropriate repository permissions.

Can an Issue have multiple labels?

Yes.

An Issue can have multiple labels at the same time.

Can Pull Requests have labels?

Yes.

Labels can be applied to Pull Requests as well.

Can I change a label later?

Yes.

Repository maintainers can generally edit label names, descriptions, and colors.

Are labels available in every repository?

GitHub repositories can use labels, though the available labels and permissions depend on the repository configuration.

GitHub Labels Example

Here's a simple example of how a development team might organize an Issue:

Issue #72

Fix Student Login Error

Labels:

🐛 bug
🔴 priority: high
💻 backend

From this alone, the team knows:

What is it?
→ Bug

How important is it?
→ High priority

Which area is affected?
→ Backend

That's the main purpose of GitHub Labels.

Summary

GitHub Labels are colored tags that help developers organize and categorize Issues and Pull Requests.

They can identify:

  • Bugs

  • Features

  • Documentation

  • Priorities

  • Technologies

  • Beginner-friendly tasks

  • Areas of a project

The basic idea is:

Issue / Pull Request
        ↓
     Labels
        ↓
Better Organization
        ↓
Faster Project Management

If you're learning GitHub, understanding Labels is an important step toward managing repositories professionally.

Labels:

Comments

Post a Comment

Popular posts from this blog

Understanding Comments in Java: A Beginner’s Guide

When learning Java programming, one of the first concepts you’ll come across is comments . Comments may not affect how a program runs, but they play a crucial role in making code more understandable, readable, and maintainable. Let’s dive deeper into what comments are, why they’re important, and the different types of comments in Java. What are Comments in Java? A comment in Java is a piece of text written within a program that is ignored by the compiler . In other words, comments are notes for humans, not instructions for machines. They help developers explain the purpose of code, describe logic, or temporarily disable certain lines of code without deleting them. Why are Comments Important? 📌 Readability – Comments make code easier to understand for you and others. 📌 Maintenance – When you revisit your code after months, comments remind you what you were doing. 📌 Collaboration – In team projects, comments explain code to fellow developers. 📌 Debugging – You c...
Post a Comment
Read more

Java Program to Check Voting Eligibility

In this program, we’ll take the user’s age as input and check whether the person is eligible to vote or not. In India, the minimum age required to vote is 18 years . 💻 Program Code // Java Program to Check Voting Eligibility import java.util.Scanner; public class VotingEligibility { public static void main(String[] args) { // Create Scanner object to take input from user Scanner sc = new Scanner(System.in); // Ask user to enter age System.out.print("Enter your age: "); int age = sc.nextInt(); // Check eligibility if (age >= 18) { System.out.println("You are eligible to vote."); } else { System.out.println("You are not eligible to vote yet."); System.out.println("You can vote after " + (18 - age) + " year(s)."); } sc.close(); // Close the scanner } } 🧠 Explanation import java.util.Scanner; → Imp...
Post a Comment
Read more

Java Program to Calculate Total Marks and Average of Five Subjects

💡 Program Explanation In this program: The user will input marks of five subjects . The program will calculate the total marks and average . It will then display both results clearly. 🧑‍💻 Java Code: // Java Program to Calculate Total Marks and Average of Five Subjects import java.util.Scanner; // Importing Scanner class for user input public class TotalAndAverage { public static void main(String[] args) { // Creating Scanner object to take input from user Scanner sc = new Scanner(System.in); // Declaring variables for five subjects double subject1, subject2, subject3, subject4, subject5; // Taking marks input for each subject System.out.print("Enter marks of Subject 1: "); subject1 = sc.nextDouble(); System.out.print("Enter marks of Subject 2: "); subject2 = sc.nextDouble(); System.out.print("Enter marks of Subject 3: "); subject3 = sc.nextDo...
Post a Comment
Read more