-
### Checklist
- [x] 1. I have searched related issues but cannot get the expected help.
- [x] 2. The bug has not been fixed in the latest version.
- [x] 3. Please note that if the bug-related issue y…
-
This came up as a question during the BA summit last week and we didn't get to talk about it properly (alas!) so I wanted to raise the issue here. @thomastaylor312 originally expressed interest in pos…
-
The merge conflicts encountered are simple enough to resolve in the GitHub UI without using a merge tool. It may be worth considering simplifying the activities to resolve the merge conflicts in that…
-
Dear GitHub Community, can anyone help me with the following problem, please?
We treated two different cell lines with our substance of interest (in triplicates) and had RNA sequencing analysis don…
-
We have the tool names in `config.js`.
The tool’s respective homepage URLs are in `shared/utils/tool-homepages.ts`. We should unify those into `config.js`.
surma updated
1 month ago
-
i dont want to use filemerge for conflicts after running `sl rebase`. would prefer to just resolve the flags in my default editor. is there some simple config im missing here?
former facebooker. lo…
-
```
A tool to merge records would be nice.
Something? http://djangosnippets.org/snippets/2213/
```
Original issue reported on code.google.com by `dmbs...@gmail.com` on 30 Jan 2012 at 7:42
-
**Problem description**
Build 1065 on MacOS 10.13.6
Sublime Merge does not support external diff/merge tools
**Preferred solution**
Allow Sublime Merge to launch a 3rd party diff/merge to…
-
https://github.com/jdh-observer/48RGuzM4qfVA
-
Hello there,
i have 400 samples, i have called SVs using manta and Smoove, i now want to merge them using SURVISOR. These the out of SVs variants have the same sample ID the difference is only the …