python-packaging / python-packaging/skel
make release with modifications should fail
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 48m
- Merged PRs (30d)
- 1
Description
We should probably stop if there are any important modifications, to avoid extra files that can't be recreated from the repo. Could also do this in another copy like
export GIT_DIR=$(realpath $(git rev-parse --git-dir)); cd $(mktemp -d); git checkout -f; ls
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
Reproduce the release with local modifications using the repository state and command shown in the issue. Trace the release entry point to identify where repository cleanliness is checked. Done means a release with important uncommitted modifications fails instead of producing files that cannot be recreated.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100