88d78a963d
Rather than having multiple CONTRIBUTING files, one for each repository, which we will need to keep in sync, we could use GitHub's special .github repository for community files. This idea was first reported by @bpo in the context of the examples repository: https://github.com/dagger/examples/pull/47#issuecomment-1012517202 I have added it as https://github.com/dagger/.github and explained how the contributing flow now changed for first-time contributors to *any* repository in our org: https://github.com/dagger/examples/pull/47#issuecomment-1013450052 There is more info on this feature here: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file We could continue by adding CODE_OF_CONDUCT, SECURITY etc. files and all our repositories will use them, without needing to add these files to each repository. Is this a GitHub feature something that fits us? Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk> |
||
|---|---|---|
| .. | ||
| tests | ||
| 1003-get-started.md | ||
| 1004-first-env.md | ||
| 1005-what_is_cue.md | ||
| 1006-google-cloud-run.md | ||
| 1007-kubernetes.md | ||
| 1008-aws-cloudformation.md | ||
| 1009-github-actions.md | ||
| 1010-dev-cue-package.md | ||
| 1011-package-manager.md | ||