autonomousapps/dependency-analysis-gradle-plugin

Create GitHub releases for corresponding tags

Open

#1,036 opened on Nov 16, 2023

View on GitHub
 (4 comments) (3 reactions) (0 assignees)Kotlin (154 forks)auto 404
documentationhelp wanted

Repository metrics

Stars
 (2,172 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. Despite having enabled watching of releases for this repo, I typically only find out about new versions of this project when I do ad-hoc runs of the Gradle Versions Plugin on one of my projects.

Describe the solution you'd like I see releases are regularly tagged, but those tags aren't flagged as releases. It would be nice if GitHub releases were created for those tags. It will allow me to test and give feedback on releases sooner due to the notifications. Also, auto-generated release notes could include links to all the GitHub issues included in the release, which I've often wished to see in the current 'CHANGELOG.md'.

Describe alternatives you've considered None.

Additional context None.

Contributor guide

Research direction
Inspect the repository's existing CI/CD workflows (e.g., .github/workflows) to see how tags are handled and if release automation already exists. Research GitHub Actions for automatically creating releases when tags are pushed, such as softprops/action gh release. Understand how the project's tags are generated (e.g., via Gradle's release plugin). Consider enabling auto generated release notes and compare with the existing CHANGELOG.md.
Tech stack
kotlin
Domain
releasebuild system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75