-
**Developer TODO (don't remove)**
- [ ] create new branch. put issue number at start of name
- [ ] update documentation
- [ ] merge and delete branch (don't squash because want commit history to se…
-
doing squash and merge is always creating new commit with new hash which make developers resolve conflict everytime they merge thier code in any branch, by doing it with commit and merge dev always ha…
-
**The problem I'm trying to solve:**
Is there a way to create a PR and tell GitHub to merge it as soon as checks are passed?
![image](https://user-images.githubusercontent.com/21138205/104021536…
-
# Create an issue
1. Create and name the issue
2. Add labels describing it (back, front, bug, enhancement...)
# Working on an issue
1. Assign yourself to an issue
4. Make a new branch fro…
-
There is a 3 years old branch "brl_reflect". Would someone mind to update it so it uses current state's of brl.mod, bcc etc?
It might close #204 and #205 (and multiple other issues from 2019).
…
GWRon updated
2 years ago
-
Hi,
I'd like to use tfnotify for a GitHub repository whose merging option is squash-and-merge, but tfnotify does not post an apply comment to the last commit (it always posts to one before the last…
-
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…
-
GitHub introduced a new API for determining which PR a commit came from, we could use this API to avoid the multiple regular expression matchers that we are having to use today (e.g. the "squash and m…
-
-
### 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…