-
Is there an easy way to squash commits?
The AI keeps committing for each message, and this litters the history. Having `/squash 3` which automatically generates a prompt message using AI and squas…
-
When merging a PR, we currently can do either "Rebase and merge" or "Squash and merge". The later we should probably not use as we try to produce nicely crafted commits in the first place and GitHub a…
-
---
name: '#5 Task'
about: 'Task that should be linked to user story #1'
title: 'Squash with Traceability to Task and PR in Commit Message Integration Strategy, but with Some Commits in the Branch …
-
Hello,
Our setup:
Version: GitLab 14.2.0-ee
The project setting has `Squash commits when merging` as required, users can't deselect the check box.
Our marge-bot user is called merge-bot
We ha…
-
## Rationale
1. This was previously attempted by the automated dependabot job but the PR tests failed.
1. This issue has been created to fix the issue as there may be multiple dependency requirement…
-
**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…
-
I was thinking about the idea of caching a separate map between Main commits and Sub commits (#3), and I was thinking about how `git push` and `git fetch` can be used to share any ref under `refs/` cr…
-
I merged much of linearfold directly from https://github.com/allyourbasepair/rbscalculator - and so, not only are the linters *very* unhappy, but there are lots of missing spots for better documentati…
-
Once the repo is public
- [x] protect master branch, require pull requests for every change
- [ ] require one positive review per PR
- [ ] merge trivial changes with one positive review
- [ ] non-…
-
### Describe the problem
Currently, our workflow with translation management centres around PRs. Whenever a change is made to one or multiple texts, a PR is created as a mean to approve changes made …