-
### Feature Description
Gitea should prevent close comments if the issue is already closed (just don't add another comment). This happens while merging a PR with squash merge - one close comment come…
-
# Release Checklist:
ℹ️ This is the checklist that I try to go through for every single release. If you're wondering why it takes so long for me to complete stable releases, this is why.
---
##…
-
**Developer TODO (don't remove)**
- [ ] create new branch. put issue number at start of name
- [ ] update documentation
- [ ] exclude the key map when you pause key maps
- [ ] squash and merge
- …
-
The companion advises to squash before pushing, but these days you can click "Squash and merge" in GitHub, which is better because it preserves the conversation.
https://github.com/ukgovdatascience…
-
**Is your feature request related to a problem? Please describe.**
I could not find a way to use quick merge options as available on GitHub online when merging in the PR.
**Describe the solution y…
-
References user story #1
## TODO:
- [x] :question: Answer question `Task4_Q1` on Canvas
- [x] :bust_in_silhouette: Assign yourself to this task (this will prompt the [WorkflowLearning GitHub App]…
-
We're currently looking up a commit's associated PR by searching for a PR with a matching `merge_commit_sha` field. This works well for squash-merged PRs, but in other cases, it leaves us with a bunc…
-
Hi, I just discovered your netradiant branch. As a radiant contributor I try to reduce the most possible the diff between living radiant branch. That's why for example I sometime backport stuff from N…
-
Hi, for the sake of retaining commit revision and authorship history, please don't squash the commits down into a single monolithic initial commit as appears to have been done here.
It's much better …
-
There needs to be some documentation added that this library is not useful if your git strategy includes Squash Merging or should include guidelines on strategy that will facilitate this package not b…