Activate pipeline institutional configs in template

[jfy133]

As this should be supported now though here: nf-core/configs#674

Meaning devs don't need to touch the section of the config, and users can add configs when they need

[github-actions]

This PR is against the master branch ❌

• Do not close this PR
• Click Edit and change the base to dev
• This CI test will remain failed until you push a new commit

---

Hi @jfy133,

It looks like this pull-request is has been made against the nf-core/tools master branch.
The master branch on nf-core repositories should always contain code from the latest release.
Because of this, PRs to master are only allowed if they come from the nf-core/tools dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page.
Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

[jfy133]

@nf-core-bot fix linting

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.23%. Comparing base (cdebded) to head (91d264b).

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mashehu]

We should merge #2404 first I think, to not add more merge conflicts there.

[jfy133]

We should merge #2404 first I think, to not add more merge conflicts there.

Would this effect that at all? Does the TUI pipeline creation effect the config file?

But OK

[mashehu]

I think we made some fine-tuning changes in the template, which could be with this file. But open for @mirpedrol to prove me wrong, when she is back. 🙂

[mirpedrol]

This PR can be merged without any conflicts with #2404, thanks for double ckecking! 🙏

[jfy133]

Woohoo1 Nice thank you all, will merge the other one on configs and 🤞 nothing breaks