Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update maintainers-minutes-2024-07-26.mdx #2686

Merged
merged 2 commits into from
Aug 16, 2024
Merged

Update maintainers-minutes-2024-07-26.mdx #2686

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
062155b
Update maintainers-minutes-2024-07-26.mdx
SPPearce Aug 16, 2024
bd11afb
Remove space at end of line to satisfy prettier
SPPearce Aug 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions sites/main-site/src/content/blog/2024/maintainers-minutes-2024-07-26.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,12 +80,12 @@ Everyone think it's a good idea and we discussed how to best approach this since

Some ideas included linking the docs with the tools version and date stamp the docs, have dev docs version to account for incremental updates.
However, it was brought up that that linting against the tools dev version may cause problems with changes that may occur during the development on the dev branch.
One of the major technical challenges that was flag was to best account for various docs versions on the website, with the additional complication the the guidelines page is planned to be split up into one file per guideline point (which [James](https://github.com/jfy133[]) finds 🤢).
One of the major technical challenges that was flagged was how to best account for various docs versions on the website, with the additional complication that the guidelines page is planned to be split up into one file per guideline point (which [James](https://github.com/jfy133) finds 🤢).
[Matthias](https://github.com/mashehu) will think about a few ways on how this could be tackled to minimise the amount of file copies that may occur when archiving each version.

## Next time

[Mahesh](https://github.com/mahesh-panchal) has figured out an interesting way to handle args in nf-tests without having to make a separate `nextflow.config` file each time for each test (as brought up here[https://nfcore.slack.com/archives/C049MBCEW06/p1721042240473589](https://nfcore.slack.com/archives/C049MBCEW06/p1721042240473589))
[Mahesh](https://github.com/mahesh-panchal) has figured out an interesting way to handle args in nf-tests without having to make a separate `nextflow.config` file each time for each test ([as brought up here](https://nfcore.slack.com/archives/C049MBCEW06/p1721042240473589)).
We'll discuss this in detail next time.

\- :heart: from your #maintainers team!
Loading