make release with modifications should fail

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
release

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.

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
Dominant language
Python
Stars
0
Forks
2
Avg merge
48m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 python-packaging/skel

All issues in python-packaging/skel

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.