-
The coding guidelines [here](https://github.com/biocommons/biocommons.github.io/blob/c1ac95dcf2b290ddd546af8e22132b1c0297de51/docs/contributing/coding-guidelines.md#coding-guidelines) should be update…
-
### Description
It would be beneficial to implement an action that automatically renames pull requests based on commit messages and changes made within the pull request. This would be particularly us…
-
I've found PRs are far more helpful in understanding changes when looking back than commit messages. Looking for any other feedback before updating our PR template to be more useful:
---
1- I thin…
-
I think it's time to say goodbye to Merge on Green bot, and I wanted to start a discussion here. GitHub recently introduced the concept of auto-merge which is available on the PR merge button:
https…
-
**Is your feature request related to a problem? Please describe.**
`release-please` currently expects all your release commits to be on the same branch you are releasing from. This doesn't work when…
-
Where I work, we've started a general policy to always squash merge our PRs. Sometimes I base new feature branches on unmerged PRs, and once those PRs are squash merged, it makes rebasing my feature b…
-
I've complained in the past [on Zulip](https://lf-lang.zulipchat.com/#narrow/stream/336350-general/topic/Merge.20Strategy/near/371093402) about the cleanliness of our git history trees.
Since our c…
-
References user story #1
:bulb: **HINT**: Feel free to click the checkboxes below (which serve as a TODO checklist for the task) as you progress through the instructions
## TODO:
- [ ] :questio…
-
With multiple developers contributing, we should have some rules in place to ensure the `main` branch stays clean and tidy. I have some suggestions based on previous experience, very much open to disc…
-
As it's possible to select which kinds of methods for "merging" a PR is allowed, i.e. any/all of these:
- merge
- rebase
- squash
Thus one can run into problems such as this one (if a repo has d…
MPV updated
11 months ago