MarineAssess updates to recipe_ocean_quadmap.yml

[SophieHall2024]

Short description of the diagnostic
Details will be added @ehogan helping with this.

Branch and pull request
Once you've started working, add the branch (and pull request)

[valeriupredoi]

@SophieHall2024 many thanks for opening this and for the subsequent work in the PR. Could I be a bother and ask you to not reference the issue in every commit in the PR, please? This makes the issue comments hard to read since one needs to scroll through countless commits referenced by GitHub. Cheers 🍺

[SophieHall2024]

OFFICIAL Yes of course, I apologise! I am still very new to this 😊 OFFICIAL From: Valeriu Predoi ***@***.***> Sent: 18 November 2024 12:42 To: ESMValGroup/ESMValTool ***@***.***> Cc: Sophie Hall ***@***.***>; Mention ***@***.***> Subject: Re: [ESMValGroup/ESMValTool] MarineAssess updates to recipe_ocean_quadmap.yml (Issue #3799) This email was received from an external source. Always check sender details, links & attachments. @SophieHall2024<https://github.com/SophieHall2024> many thanks for opening this and for the subsequent work in the PR. Could I be a bother and ask you to not reference the issue in every commit in the PR, please? This makes the issue comments hard to read since one needs to scroll through countless commits referenced by GitHub. Cheers 🍺 — Reply to this email directly, view it on GitHub<#3799 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJVCWTEGVIJ7TJ4RVU6ZQ2L2BHOBTAVCNFSM6AAAAABRD45FDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBSHEZTINRQGQ>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[valeriupredoi]

@SophieHall2024 absolutely no worries, we've all been new to GitHub at some point 😃 Cheers!

[ehogan]

@valeriupredoi, I often recommend adding the issue number to the start of a commit message (then the commit messages show up on the issue rather than the PR), and I haven't yet spent a lot of time with @SophieHall2024 on GitHub yet, so apologies (to both of you!) for the confusion! 😊

[valeriupredoi]

no worries at all @ehogan 🍺 Many commits to a PR with the issue number tagged in, will result in a lot of traffic on the issue, whereas discussion items might get lost, if you add the issue number without a # then it's fine, that won't get piped through as references; having said that, if you would like to highlight a particular commit of interest, then either get the commit hash, or do indeed tag the issue in it like here 🍺