-
# Problem
Recently we merged #5596 with `Squash and Merge` feature. It formed this f05b7e793dfd500d72ca92d08e1ab5e7ee5576ed with message:
```
[CHERRY-PICK] PRs #5581 #5557 (#5596)
```
And now…
-
### Current Behavior
When multiple changes are made to a package and are added to the base branch through the "squash and merge" option from github at merge time, launching nx release version on the …
-
We like our commit history to be clean. During code review it's not uncommon for the first commit to have a useful commit message while other commits in the PR have messages like `update code for code…
-
-
I got a sqlite error when attempting this migration:
```ucm
.blarg> pull-request.load git(https://github.com/unisonweb/base:v3):.trunk git(https://github.com/tarik-ozkanli/allmyunisoncode)
🔨 Migr…
-
# Motivation
We would like to have a repository module, to handle the organization repositories. To start, we want to manage the following properties of the repo, the will be ignored by terraform:
…
-
It seems like it would be worth setting up a [merge queue](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-wi…
-
Currently, we are using the "squash" method from tide (the merger component of Prow)
This pose some problems:
- Dependents PRs (PRs with a starting point being the tip of another PR, useful when s…
-
### Expected Behavior
When I run a `terraform plan` for `github_repository` resources, which have `allow_squash_merge` set to `false`, I should not see any values for `squash_merge_commit_message` an…
-
Bumps [Verify.Xunit](https://github.com/VerifyTests/Verify) from 25.3.1 to 26.1.5.
Commits
aebefe7 Argon 0.19.0
c57f764 Update Directory.Build.props
188b8ae Update Directory.Packages.props
56e79d9 U…