Adding optional parameter - create annotated git tag

Open Beginner friendly
#332 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python
Domain
release

Research direction

Start by locating the action input schema and the generator entrypoint where git tags are currently handled, then wire in a new optional tag-creation input. Trace the existing flow for missing/creating tags and adjust behavior so true creates when absent (warn if already present) and false explicitly skips creation with a loud failure. Run the project’s normal tests or CI check for release-note generation, and verify docs/examples describe the new option and its expected outcomes.

Written by the indexing model from the issue text.

Description

enhancement
Feature Description

Currently, with the newest version of v1.3.2, the Release Notes Generator does assume that the Git Tag already exists. If it does not exist, the action fails.

The way we solved this is that we explicitly create the Git Tag one step before the Release Notes Generator - but this is logically so close to the RN generator workflow, that it could be part of it - configurable by user.

Problem / Opportunity

Every CI action involving RN Generator must have a git tag creation there. Since this is used on almost every repository, our CI files could be slightly simpler - reducing git tag creation code.

Acceptance Criteria

The RN generator contains 1 optional parameter, maybe boolean tag-creation or something like that.

  • If it's true, then it will be created (and if it exists already maybe it should just emit warning).
  • If false then it should not create tag and it should fail loudly.
Dominant language
Python
Stars
13
Forks
0
Avg merge
6h 50m
Merged PRs (30d)
7

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.

More from AbsaOSS/generate-release-notes

All issues in AbsaOSS/generate-release-notes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.