-
When I click on the "Squash and Merge" button for a generated backport PR, I end up with a commit title that has 2 different PR numbers in it: the original and the new one. I'd expect only the new PR…
-
### Problem Statement
I have noticed that when the "Suspect Commit" feature is used to identify the commit likely responsible for a bug, it often points to merge commits from the master or main branc…
-
**Developer TODO (don't remove)**
- [ ] create new branch. put issue number at start of name
- [ ] option to send a predetermined message or show a prompt to choose the message
- [ ] option to inst…
-
Hello Sublime Merge team!
**Problem description**
Imagine a situation:
* There is a repository in GitHub where Pull Requests are allowed to be merged only by "Squash and merge".
* Developer pu…
-
**Developer TODO (don't remove)**
- [ ] create new branch. put issue number at start of name
- [ ] update documentation
- [ ] squash and merge
- [ ] delete branch
we should we able to cycle throu…
-
### Description
When running `ctr images` with `--force` at the end, containerd treats the `--force` flag as an image and fails. This previously worked on 1.X branches.
### Steps to reproduce the is…
-
Would it be possible to talk about the `git squash` command? Since it will shrink several git commits down to one commit and can be potentially helpful when merging to master branch.
It is a very u…
-
I have put up a draft of how our workflow should be:
```markdown
# Workflow
This will be guide to the workflow of the project.
## Commit messages
As detailed by the judging guide so will …
-
### Problem
### A clear and concise description of what you want to happen
Being able to look at a history (e.g., ) and have some way to see (possibly) related edits (e.g., by the same editor/acco…
Freso updated
3 weeks ago
-
Can we have dedicated field to edit squashed commit message ?
Instead of "squash branchname", i want to give the message like this "Merged PR (#...)" ..
It will be a great help for me and my team ..…