2 comments (2 comments)1 reaction (1 reaction)0 assignees (0 assignees)Python1,253 stars (1,253 stars)162 forks (162 forks)batch import
Difficulty: NewcomerHacktoberfestenhancementhelp wanted
Description
Need to have better debug logging in place for HubCommander.
Contributor guide
- Tech stack
- python
- Domain
- backend
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- basic Python knowledgefamiliarity with HubCommander codebase
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 60
- Research direction
- Start by exploring the HubCommander codebase to understand the current logging setup. Look for any existing logging statements in files like hubcommander/bot.py or main.py to identify where debug logging could be improved. Consider adding logging for key events such as command execution, error handling, and external API calls. Since the issue is broad, you may need to propose a specific plan in the issue comments before implementation.