MerginMaps / MerginMaps/mobile
Zenodo points to development version
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
We updated Zenodo to bear the current version as is inside info.plist (or other files with version), however, most of the time this is a development version, not the latest release. It might be better to have it point to the latest GitHub release.
Possible solution: On GitHub release run an Action that will create PR with updated version in the Zenodo file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Zenodo version in info.plist or the other version files, then inspect the repository's GitHub release workflow or Actions configuration. Define the release trigger and verify that it creates a PR updating Zenodo to the latest GitHub release rather than the development version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100