add draft to guidelines from slack discussion

[lpantano]

Following slack discussion we agree on adding some text on PR review to make it more transparent to new people or as a reminder.

@netlify /docs/tutorials/contributing_to_nf-core/contributing_to_pipelines

[netlify]

✅ Deploy Preview for nf-core-main-site ready!

Name	Link
🔨 Latest commit	0a46cba
🔍 Latest deploy log	https://app.netlify.com/sites/nf-core-main-site/deploys/6722a6ddfddb0000084c313b
😎 Deploy Preview	https://deploy-preview-2780--nf-core-main-site.netlify.app/docs/tutorials/contributing_to_nf-core/contributing_to_pipelines
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for nf-core-docs ready!

Name	Link
🔨 Latest commit	0a46cba
🔍 Latest deploy log	https://app.netlify.com/sites/nf-core-docs/deploys/6722a6dd2329f6000824da2d
😎 Deploy Preview	https://deploy-preview-2780--nf-core-docs.netlify.app/docs/tutorials/contributing_to_nf-core/contributing_to_pipelines
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ewels]

Needs a little polishing yet I think, left a few comments. Nothing major though.

What do folks think about having this as a new dedicated Guidelines page and linking to it from here?

I had envisioned it more as a set of rules / standards that we follow rather than instructions in a tutorial tbh..

[ewels]

Link to docs for first release

[lpantano]

sorry, I cannot find exactly this? I found pipeline release but not first release

[ewels]

One to add: "request changes" reviews can be dismissed by the PR author if considered out of date and resolved.

Link to the GitHub docs on this to explain how to do it.

[ewels]

Also maybe some mention that it's fine / encouraged for other people to push to your PR. For example fixing linting (can mention bot commands) but also to build on or fix code if appropriate.

[jfy133]

Couple of prhasing tweaks but overall LGTM after the indentation from Phil (agree reads a bit weird as they are explanation)

[lpantano]

thanks! I made a bunch of changes following the comments, much better now, not sure if I am 100% in the indents of all the points, let me know.
Agree to have it outside tutorial, are you thinking Guidelines/Pipelines?

[lpantano]

or just under Guidelines?

[lpantano]

@ewels and @jfy133 , I think this is almost there. Just need to figure out the final place for this. Is inside Guidelines a good place?

[jfy133]

Ugh sorry @lpantano ! The first re-review request got buried in my notifications 🙈 Feel free to bother me on slack next time :)

Re the location: Reading through it I think a guidelines page would make sense - you use a lot of 'SHOULD' language which would fit, but if we do move there I feel we need to tweak the language to follow e.g. the modules guidelines (with a strict definition of SHOULD/MUST/MUST NOT) etc.

Each major point in this list should be become it's own header which we can then number using that astro plugin @mashehu has added to the top of e.g. the modules guidelines, and we can 'cite' them.

[jfy133]

@nf-core-bot fix linting