Skip to content

feat: Adding Github Templates for Issues and PRs#732

Merged
bupd merged 4 commits into
goharbor:mainfrom
NucleoFusion:main
Mar 8, 2026
Merged

feat: Adding Github Templates for Issues and PRs#732
bupd merged 4 commits into
goharbor:mainfrom
NucleoFusion:main

Conversation

@NucleoFusion

Copy link
Copy Markdown
Contributor

Changes

Issue

https://github.com/NucleoFusion/harbor-cli/issues
You can view the 3 types of issues here

Bug

---
name: Bug Issue 
about: Report a bug 
title: "[bug]: "
labels: "bug"
---

## Description
A clear and concise description of the bug.

## Steps to Reproduce
1. Run command: `...`
2. With arguments/config: `...`
3. Observe error

## Expected Behavior
What you expected to happen.

## Actual Behavior
What actually happened.

## Environment
- OS:
- Tool version:
- Other relevant details:

## Additional Context
Logs, screenshots, or other useful information.

Feature

---
name: Feature Request
about: Suggest a new feature or improvement
title: "[feature]: "
labels: enhancement
---

## Problem
What problem does this feature solve?  
Describe the limitation or pain point you are facing.

## Proposed Solution
Describe the feature or behavior you would like to see.

## Alternatives Considered
Have you considered any alternative approaches or workarounds?

## Additional Context
Add any other context, examples, or references here.

Enhancement

---
name: Discussion
about: Ask a question or start a discussion
title: "[discussion]: "
labels: discussion
---

## Topic
What would you like to discuss?

## Context
Provide any background or details that help explain the topic.

## Possible Ideas / Thoughts
(Optional) Share any ideas or approaches you already have.

## Additional Information
Links, examples, or anything else relevant.

PS: This requires a discussion label

Pull Requests

https://github.com/NucleoFusion/harbor-cli/pulls
You can view the PR template here

## Description
Briefly describe what this pull request does and why the change is needed.

Fixes #

## Type of Change
Please select the relevant type.

- [ ] Bug fix
- [ ] New feature
- [ ] Refactor
- [ ] Documentation update
- [ ] Chore / maintenance

## Changes
- 
- 
- 

Other Considerations

CODEOWNERS

The purpose of this file is to automatically request reviews from the right maintainers when a pull request changes certain parts of the codebase. Instead of manually assigning reviewers, GitHub will do it automatically based on which files were modified.

This helps ensure that:

  • Changes are reviewed by someone familiar with that part of the project
  • Maintainers don’t forget to request reviewers
  • Pull request reviews become more consistent
# Default owner for the entire repository
* @project-maintainer


# CLI commands
cmd/ @cli-maintainer


# Core internal logic
internal/ @core-maintainer


# Public libraries or packages
pkg/ @library-maintainer


# Documentation files
docs/ @docs-maintainer
*.md @docs-maintainer


# GitHub workflows and automation
.github/workflows/ @infra-maintainer


# Dependency configuration
.github/dependabot.yml @infra-maintainer

Labeler(.yml)

The goal is to reduce manual triage work by automatically applying labels based on:

  • Files changed in a pull request
  • Selections made in issue templates (checkboxes)

This helps maintainers quickly understand the type and scope of a contribution and keeps issue and PR organization consistent.


How It Works

A GitHub Action runs whenever an issue or pull request is created.

For pull requests, labels are applied based on the files that were modified.

Example configuration:

documentation:
  - "docs/**"
  - "*.md"

cli:
  - "cmd/**"

core:
  - "internal/**"

If a pull request modifies a file like:

docs/usage.md

GitHub will automatically apply the label:

documentation

Labeling Issues from Template Selections

Issue templates include a checklist where contributors select the type of issue.

Example:

## Type

- [ ] Bug
- [ ] Feature request
- [ ] Documentation

When an issue is opened, the workflow reads the selected checkbox and automatically applies the corresponding label.

Example selection:

[x] Bug

Result:

label applied → bug


Benefits

  • Reduces manual labeling effort
  • Helps maintainers quickly triage issues and pull requests
  • Keeps issue and PR labels consistent
  • Makes filtering and searching issues easier
  • Improves contributor experience by organizing issues automatically

@qcserestipy @Vad1mo @bupd Thoughts?

Signed-off-by: NucleoFusion <lakshit.singh.mail@gmail.com>
Signed-off-by: NucleoFusion <lakshit.singh.mail@gmail.com>
Signed-off-by: NucleoFusion <lakshit.singh.mail@gmail.com>
@codecov

codecov Bot commented Mar 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 7.45%. Comparing base (60ad0bd) to head (ab186dd).
⚠️ Report is 108 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##             main    #732      +/-   ##
=========================================
- Coverage   10.99%   7.45%   -3.54%     
=========================================
  Files         173     261      +88     
  Lines        8671   12930    +4259     
=========================================
+ Hits          953     964      +11     
- Misses       7612   11857    +4245     
- Partials      106     109       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Updated pull request template to include a placeholder for issue fixes.

Signed-off-by: Prasanth Baskar <bupdprasanth@gmail.com>

@bupd bupd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@bupd bupd changed the title feat: Adding github templates for issues and PRs feat: Adding Github Templates for Issues and PRs Mar 8, 2026
@bupd bupd merged commit bf5ca95 into goharbor:main Mar 8, 2026
6 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants