Documentation: deploying & squash merges
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
You should not deploy from a branch, then squash merge that branch. It changes (removes) the commit hash of the commit that created the deployed package. This fact should be documented 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
No documentation file or test is named; first locate the project's deployment and release documentation. Document that deploying from a branch before squash-merging it changes the commit hash that created the deployed package, and confirm the warning appears where deployment guidance is maintained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100