Tagging releases
- Dominant language
- Python
- Stars
- 77
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Hello. When reviewing the README, I noticed many releases in the [changelog](https://github.com/esa/opengeode#changelog). Was thinking it might be helpful to consider [tagging the releases](https://docs.github.com/en/github/administering-a-repository/managing-releases-in-a-repository) so potential contributors or others downstream might get a clearer point of reference.
Or maybe at least for significant point releases.
Anyhow, just an idea.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the README changelog and GitHub's repository-release guidance first. Identify which listed releases should receive tags or GitHub releases, then confirm that the chosen releases are visible as clear historical reference points for contributors and downstream users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100