-
I would like to be able to have the default merge action for a repo created with `github_repository` have a default merge action that is configurable.
By default I want users to `Squash and Merge` …
-
For repositories that use Merge for PRs, merging a stack of PRs is very easy.
Given a stack `main -> feature1 -> feature2`, you can merge feature1, and then feature2.
No additional work is needed.
…
-
Since PR's are squash merged, their commit into main will be named after the PR itself. It is redundant to enforce commit names since they will not show up in the protected branch anyways.
-
It would be a really nice feature if the parsing handled commits squashed by github. Seemingly the only way to get it working is either a merge commit or rebase merge but convention (at least where I …
-
# Feature or enhancement
### Proposal:
(split off of https://github.com/python/cpython/issues/99633#issuecomment-2380302948 to keep related pull requests and discussion better organized)
Star…
-
Bumps [JsonSchema.Net.Generation](https://github.com/gregsdennis/json-everything) from 3.5.1 to 4.1.1.
Commits
98bc29d Merge pull request #447 from gregsdennis/schema/unix-file-uris
9267cff update r…
-
### Version
0.13.0
### Operating System
Windows
### Distribution Method
msi (Windows)
### Describe the issue
When a PR was merged upstream, the virtual branch was not removed while syncing:
…
-
References user story #1
## TODO:
- [ ] :question: Answer question `Task3_Q1` on Canvas
- [ ] :bust_in_silhouette: Assign yourself to this task (this will prompt the [WorkflowLearning GitHub App]…
-
Some communities are very adamant about _never_ squashing commits, instead using commits to describe logical bits of change and then just merging them all in to preserve the blame. While…
kpk47 updated
3 months ago
-
### Is there an existing feature request for this?
- [X] I have searched the existing issues.
### Command
_No response_
### Description
I would love to be able to set up Melos such that only merg…