woodpecker-ci / woodpecker-ci/plugin-git

Print plugin version ...

Open
#384 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
25
Forks
40
Avg merge
22h 23m
Merged PRs (30d)
6

Description

add some debug info ... e.g. as this plugin is often implizite used, and version is only internally pinned, we shoud at least give the use some info to debug stuff ...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the plugin's startup path and existing debug or version output. Identify where the plugin version is defined or supplied, then expose it in the plugin's diagnostic output and verify that it is visible when the plugin runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
ci-cd, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.