-
### Description
When a commit is not linked to an issue it can bring a number of problems:
* An issue may be open, but not automatically closed when the commit is merged
* Harder to track back-po…
-
**What happened**:
**What you expected to happen**:
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- Kubernetes v…
-
### The problem
# You have long waiting Time upon clicking on **History**?
# You get stuck waiting for **History** to open?
# Your Github Desktop crashes after a few seconds and you see the error…
-
How do we feel about git hygiene when merging? I personally tend to squash-and-merge PRs, except if git history is particularly clean (this happens very rarely for me). Any thoughts?
When people …
-
### Terraform Version
0.14.1
### Affected Resource(s)
- `github_team_repository`
### Terraform Configuration Files
```hcl
# root module main.tf
terraform {
required_version = "= 0.14…
wsams updated
1 month ago
-
Hi, I realized that git history is a little bit dirty
![dirty log](https://user-images.githubusercontent.com/29402115/169563402-8db287f8-3578-4028-8aa2-81f13394112f.png)
suggestions:
- I think …
-
When the automerge feature is enabled, but the target branch only supports linear history (i.e. not merge commits), atlantis fails to squash/merge the commit to the target branch after successful appl…
-
As we merged bitcoin 0.17 (#41) we are now going to merge 0.18 (#727). Merging bitcoin 0.17 happened a bit chaotic: #1013 (squash), #1038 (revert), #1039 (merge).
In general when merging anything t…
-
### Feature Description
When we do a PR and there is a review, we have to push new commits to fix things. We usually take advantage of git's autosquash feature, so the new commits are prefixed with `…
-
After my initial hands-on with the PRegress package, I can see it holds great potential, especially for users familiar with performing similar analyses in R who are transitioning to Python. This means…