James A. Fellows Yates

Results 230 issues of James A. Fellows Yates

### Checklist - [x] I have reviewed the existing MIxS checklists and extensions for no terms that may overlap with the proposed updates ### Name of term to be updated...

1-TermUpdate

### Checklist - [x] I have reviewed the existing MIxS checklists and extensions for no terms that may overlap with the proposed updates ### Name of term to be updated...

1-TermUpdate

### Checklist - [x] I have reviewed the existing MIxS checklists and extensions for no terms that may overlap with the proposed updates ### Name of term to be updated...

1-TermUpdate

A major blocker for new contributors to the MIxS project is the lack of and quality of documentation. Without clear and well structured documentation, potential contributors will walk away as...

documentation-internal
documentation-external

_As discussed on 2025-07-31 at the GSC25 working group day_ All of the NMDC, aDNA and eDNA working groups said a very large problem when communicating with their communities on...

high priority

_Please point me to the relevant part in documentation if this does already exist, I tried searching but couldn't find it_ ## Context The diff output is very useful for...

I would like to compare two CSV/TSV files, and see what the differences are on a row _and_ column wise basis (i.e., I would like to know which row has...

## Bug report We are semi-regularly getting the following `ConcurrentModificationException` error on [nf-core/createtaxdb](https://github.com/nf-core/createtaxdb). See the error and stack trace below. It happens particularly regularly on [GitHub actions](https://github.com/nf-core/createtaxdb/actions/runs/19387593929/job/55476779504), but also sometimes...

This PR partly addresses as first step https://github.com/nf-core/website/issues/3653 1. Moves location of `CONTRIBUTING.md` to [`docs/`](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors) - to centralise all docs that should be displayed on the website for a pipeline...

Currently every PR on an nf-core pipeline repository will run the tests on both latest stable and edge release. However because of nf-test sharding we don't actually report a failure...