Skip to content
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

.github Bridge (docs) update #5

Open
wants to merge 22 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 20 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 0 additions & 28 deletions .github/CODE_OF_CONDUCT.md

This file was deleted.

11 changes: 0 additions & 11 deletions .github/ISSUE_TEMPLATE/security.md

This file was deleted.

172 changes: 0 additions & 172 deletions .github/ReadmeTemplate/Documentation-Style-Guide.md

This file was deleted.

92 changes: 0 additions & 92 deletions .github/ReadmeTemplate/ReadmeTemplate.md

This file was deleted.

81 changes: 81 additions & 0 deletions CODEOWNERS.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
# If we choose to use the codeowners functionality update the file as a .md then uncomment and update the following:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment makes me think this is meant more as a template than as an org-wide article?

Copy link
Member

@justincorrigible justincorrigible Nov 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which leads me to ask both what the original source if the template is, and are there instructions anywhere on what these templates are for? e.g. "when creating a new repo you will find these X and Y and Z files, which are used in the following scenarios..." etc.

do we have that somewhere I've missed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is completely optional if you don't want it than we can remove it just wanted to offer all that is possible


<!--
# Each line is a file pattern followed by one or more owners.

# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence,
# @global-owner1 and @global-owner2 will be requested for
# review when someone opens a pull request.
* @global-owner1 @global-owner2

# Order is important; the last matching pattern takes the most
# precedence. When someone opens a pull request that only
# modifies JS files, only @js-owner and not the global
# owner(s) will be requested for a review.
*.js @js-owner

# You can also use email addresses if you prefer. They'll be
# used to look up users just like we do for commit author
# emails.
*.go [email protected]

# Teams can be specified as code owners as well. Teams should
# be identified in the format @org/team-name. Teams must have
# explicit write access to the repository.
/apps/ @organization/app-team

# In this example, @doctocat owns any files in the build/logs
# directory at the root of the repository and any of its
# subdirectories.
/build/logs/ @doctocat

# The `docs/*` pattern will match files like
# `docs/getting-started.md` but not further nested files like
# `docs/build-app/troubleshooting.md`.
docs/* [email protected]

# In this example, @octocat owns any file in an apps directory
# anywhere in your repository.
apps/ @octocat

# In this example, any change inside the `/scripts` directory
# will require approval from @doctocat or @octocat.
/scripts/ @doctocat @octocat

# In this example, @octocat owns any file in the `/apps`
# directory in the root of your repository except for the `/apps/github`
# subdirectory, as its owners are left empty.
/apps/ @octocat
/apps/github -->


<!-- ## Example Here
# Overall ownership
* @overture-stack/coreMaintainers

# Workflow files
/.github/workflows/ @overture-stack/devops

# Issue templates
/.github/ISSUE_TEMPLATE/ @overture-stack/outreach

# Documentation files
*.md @overture-stack/outreach

# Security-related files
/SECURITY.md @overture-stack/coreMaintainers

# Community health files
/CODE_OF_CONDUCT.md @overture-stack/outreach
/CONTRIBUTING.md @overture-stack/outreach

# Funding related files
/FUNDING.yml @overture-stack/managers

# Standards directory
/Standards/ @overture-stack/outreach

# Profile directory
/profile/ @overture-stack/outreach
-->
Loading