luanti-org / luanti-org/contentdb
Cannot create releases from git tags not on main branch
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 115
- Forks
- 62
- Avg merge
- 19h 7m
- Merged PRs (30d)
- 5
Description
Summary
It appears like you cannot create releases from tags which do not exist on the main branch. The task which creates the release gets the error message 'error: pathspec '0.99.1' did not match any file(s) known to git'.
Encountered this because we backported a fix to earlier Mineclonia versions. Managed to work around it by uploading using zip archives instead.
Steps to reproduce
- Push a tag to the source repo (that is not on the main branch)
- Create contentdb release and specify that tag as a git reference
Note that this is just a theory, but I am pretty confident this is the problem I was having.
Not sure if you think its worth fixing, but thought I would let you know. Might be worth documenting somewhere.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the contentdb release flow with a Git tag that is not on the main branch, then inspect the task that creates the release and handles the Git reference. Done means a release can be created from that tag without the pathspec error; verify the behavior using the reproduction steps in this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100