-
Notifications
You must be signed in to change notification settings - Fork 3
Adds discussion FAQs #94
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a couple of typos
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ran through reading age checker and was happy with the result. There are a few trivial suggestions but should not block.
Co-authored-by: pwhybra <[email protected]>
Co-authored-by: Tim Pillinger <[email protected]> Co-authored-by: Ruth Comer <[email protected]>
Co-authored-by: Tim Pillinger <[email protected]>
Auto-generated via `{sandpaper}` Source : b7dca18 Branch : main Author : Dimitrios Theodorakis <[email protected]> Time : 2025-03-12 17:04:51 +0000 Message : MetOffice#94 Adds discussion FAQs * Adds discussion FAQs * Emphasise origin and upstream Co-authored-by: pwhybra <[email protected]> * Spelling and word choice fixes Co-authored-by: Tim Pillinger <[email protected]> Co-authored-by: Ruth Comer <[email protected]> * Apply reading age suggestions Co-authored-by: Tim Pillinger <[email protected]> * Add a GitHub docs link for git fetch --------- Co-authored-by: pwhybra <[email protected]> Co-authored-by: Tim Pillinger <[email protected]> Co-authored-by: Ruth Comer <[email protected]>
Auto-generated via `{sandpaper}` Source : e1cf5ee Branch : md-outputs Author : GitHub Actions <[email protected]> Time : 2025-03-12 17:06:00 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : b7dca18 Branch : main Author : Dimitrios Theodorakis <[email protected]> Time : 2025-03-12 17:04:51 +0000 Message : MetOffice#94 Adds discussion FAQs * Adds discussion FAQs * Emphasise origin and upstream Co-authored-by: pwhybra <[email protected]> * Spelling and word choice fixes Co-authored-by: Tim Pillinger <[email protected]> Co-authored-by: Ruth Comer <[email protected]> * Apply reading age suggestions Co-authored-by: Tim Pillinger <[email protected]> * Add a GitHub docs link for git fetch --------- Co-authored-by: pwhybra <[email protected]> Co-authored-by: Tim Pillinger <[email protected]> Co-authored-by: Ruth Comer <[email protected]>
5. Can you have chains of forks? Or a colleagues fork as a remote? | ||
Yes to both! Although the latter would be an unusual working practice, | ||
we'd recommend seeking advice before adding a colleague's fork | ||
as another remote on your local repository. | ||
Chains of forks are common. If a GitHub user has read access to your | ||
repository they can create a fork. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry am late to the party, but why is having a colleague's fork as a remote considered unusual? If anything I'd say this is more likely to happen than chain of forks, which only really happens in open-source-land and is unlikely to be useful for MetOffice organisation repos?
Fixes #5