├── README.md
├── CONTRIBUTING.md
├── SECURITY.md
├── config
└── repolinter-ruleset.json
├── profile
└── README.md
└── CODE_OF_CONDUCT.md
/README.md:
--------------------------------------------------------------------------------
1 | # .github
2 |
3 | *Community health files for the [@GitHub](https://github.com/github) organization*
4 |
5 | For more information, please see the article on [creating a default community health file for your organization](https://help.github.com/en/articles/creating-a-default-community-health-file-for-your-organization).
6 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | ## Contributing
2 |
3 | Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
4 |
5 | Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the project's open source license.
6 |
7 | Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
8 |
9 | ## Submitting a pull request
10 |
11 | 0. Fork and clone the repository
12 | 0. Configure and install the dependencies: `script/bootstrap`
13 | 0. Make sure the tests pass on your machine: `script/cibuild`
14 | 0. Create a new branch: `git checkout -b my-branch-name`
15 | 0. Make your change, add tests, and make sure the tests still pass
16 | 0. Push to your fork and submit a pull request
17 | 0. Pat your self on the back and wait for your pull request to be reviewed and merged.
18 |
19 | Here are a few things you can do that will increase the likelihood of your pull request being accepted:
20 |
21 | - Follow standards for style and code quality.
22 | - Write tests.
23 | - Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
24 | - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
25 |
26 | ## Resources
27 |
28 | - [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
29 | - [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
30 | - [GitHub Help](https://help.github.com)
31 |
--------------------------------------------------------------------------------
/SECURITY.md:
--------------------------------------------------------------------------------
1 | Thanks for helping make GitHub safe for everyone.
2 |
3 | ## Security
4 |
5 | GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub).
6 |
7 | Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation.
8 |
9 | ## Reporting Security Issues
10 |
11 | If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
12 |
13 | **Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
14 |
15 | Instead, please send an email to opensource-security[@]github.com.
16 |
17 | Please include as much of the information listed below as you can to help us better understand and resolve the issue:
18 |
19 | * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
20 | * Full paths of source file(s) related to the manifestation of the issue
21 | * The location of the affected source code (tag/branch/commit or direct URL)
22 | * Any special configuration required to reproduce the issue
23 | * Step-by-step instructions to reproduce the issue
24 | * Proof-of-concept or exploit code (if possible)
25 | * Impact of the issue, including how an attacker might exploit the issue
26 |
27 | This information will help us triage your report more quickly.
28 |
29 | ## Policy
30 |
31 | See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor)
32 |
--------------------------------------------------------------------------------
/config/repolinter-ruleset.json:
--------------------------------------------------------------------------------
1 | {
2 | "$schema": "https://raw.githubusercontent.com/prototypicalpro/repolinter/master/rulesets/schema.json",
3 | "version": 2,
4 | "axioms": {},
5 | "rules": {
6 | "license-file-is-MIT": {
7 | "level": "warning",
8 | "rule": {
9 | "type": "file-contents",
10 | "options": {
11 | "globsAll": ["LICENSE*", "COPYING*"],
12 | "nocase": true,
13 | "fail-on-non-existant": true,
14 | "content": "MIT License"
15 | }
16 | },
17 | "fix": {
18 | "type": "file-create",
19 | "options": {
20 | "file": "LICENSE",
21 | "replace": true,
22 | "text": { "url": "https://opensource.org/licenses/MIT" }
23 | }
24 | },
25 | "policyInfo": "MIT License is required for code or legal approval for an alternative",
26 | "policyUrl": "https://github.com/github/open-source/blob/main/policies/release.md"
27 | },
28 | "readme-file-exists": {
29 | "level": "warning",
30 | "rule": {
31 | "type": "file-existence",
32 | "options": {
33 | "globsAny": ["README*"],
34 | "nocase": true
35 | }
36 | },
37 | "fix": {
38 | "type": "file-create",
39 | "options": {
40 | "file": "README.md",
41 | "text": { "url": "https://raw.githubusercontent.com/newrelic/open-source-tools/master/nerdpacks/oss-template/README.md" }
42 | }
43 | },
44 | "policyInfo": "GitHub requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further",
45 | "policyUrl": "https://github.com/github/open-source/blob/main/policies/release.md"
46 | },
47 | "codeowners-file-exists": {
48 | "level": "warning",
49 | "rule": {
50 | "type": "file-existence",
51 | "options": {
52 | "globsAny": ["CODEOWNERS*", "*/CODEOWNERS*", ".github/CODEOWNERS*"],
53 | "nocase": true
54 | }
55 | },
56 | "fix": {
57 | "type": "file-create",
58 | "options": {
59 | "file": "CODEOWNERS",
60 | "text": { "url": "https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners" }
61 | }
62 | },
63 | "policyInfo": "GitHub requires a CODEOWNERS file in all projects. This enables GitHub to contact the maintainers in the event it is necessary.",
64 | "policyUrl": "https://github.com/github/open-source/blob/main/policies/release.md"
65 | },
66 | },
67 | "formatOptions": {
68 | "disclaimer": "🤖*This issue was automatically generated by [repolinter-action](https://github.com/newrelic/repolinter-action), developed by the Open Source and Developer Advocacy team at New Relic.*"
69 | }
70 | }
71 |
--------------------------------------------------------------------------------
/profile/README.md:
--------------------------------------------------------------------------------
1 | ## Hey, this is us 👋
2 |
3 | 
4 |
5 | Yes, we are building GitHub on GitHub. In fact, we’ve been doing this since **October 19th, 2007**. That's when we made our first commit. Since then we pushed **over 2.5 million commits**, opened **over 1 million issues**, submitted roughly **650k pull requests** across **4357 repositories** from over **50 countries**. 🤯 But that's just us. We are proud to be part of the work of millions of developers, companies and robots across the solar system. 🪐 Yes, [Robots](https://github.com/readme/featured/nasa-ingenuity-helicopter)!
6 |
7 | ### 🍿 An interconnected community
8 |
9 | The open source community is the 💗 heart of GitHub and fundamental to how we build software today. See for yourself:
10 |
11 | - [GitHub Sponsors](https://github.com/sponsors) helped support more than **5k** individuals and projects around the world 🌍
12 | - Open source projects on GitHub received a stunning **218 million** contributions 🚀 in the last year alone
13 | - **Every minute** a developer creates a new release 🏄 for a public project on GitHub
14 |
15 | Now that we are talking about the important things, ☝️ are you contributing to open source? Yes? Okay, you rock! 🎸 If not, we can help you get started! Open source software is made by people just like you. Learn more about [how to contribute](https://opensource.guide/).
16 |
17 | ### 🦦 Contributing to the ecosystem
18 |
19 | We contribute to the tools 🔧 we rely on to build and run GitHub, while also maintaining 🧙♂️ our own open source projects like:
20 |
21 | - [GitHub CLI](https://github.com/cli/cli) - A command line tool for GitHub
22 | - [GitHub Desktop](https://github.com/desktop/desktop) - A visual approach to using Git with GitHub
23 | - [Git Large File Storage](https://github.com/git-lfs/git-lfs) - A Git extension for versioning large files
24 | - [Primer](https://github.com/primer/css) - The GitHub design system
25 |
26 | ### 👓 Appendix
27 |
28 | See what's next on our [public roadmap](https://github.com/github/roadmap) ✨ and [let us know](https://github.com/github/feedback) if you have any suggestions. 🙇♂️ Oh, and by the way, we are always hiring talented, passionate people to [join our team](https://github.com/about/careers). 🙌
29 |
30 |
31 | "Tell me more, I can't get enough!"
32 |
33 |
34 | - GitHub is built using mighty 🔨 open source technologies like Ruby on Rails, Go, Primer, React and Kafka among others.
35 | - The three open source projects GitHub members have most contributed 👩💻 to are:
36 |
41 |
42 | - By the way, our documentation 🤓 is also open sourced.
43 |
44 |
45 |
46 | ---
47 |
48 | 🤫 Psst! You can create your own [organization README](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile).
49 |
50 |
54 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, caste, color, religion, or sexual
10 | identity and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the overall
26 | community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or advances of
31 | any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email address,
35 | without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | * Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | * Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | * This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | * Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | support@github.com.
64 |
65 | * All complaints will be reviewed and investigated promptly and fairly.
66 |
67 | * All community leaders are obligated to respect the privacy and security of the
68 | reporter of any incident.
69 |
70 | ## Enforcement Guidelines
71 |
72 | * Community leaders will follow these Community Impact Guidelines in determining
73 | the consequences for any action they deem in violation of this Code of Conduct:
74 |
75 | ### 1. Correction
76 |
77 | **Community Impact**: Use of inappropriate language or other behavior deemed
78 | unprofessional or unwelcome in the community.
79 |
80 | **Consequence**: A private, written warning from community leaders, providing
81 | clarity around the nature of the violation and an explanation of why the
82 | behavior was inappropriate. A public apology may be requested.
83 |
84 | ### 2. Warning
85 |
86 | **Community Impact**: A violation through a single incident or series of
87 | actions.
88 |
89 | **Consequence**: A warning with consequences for continued behavior. No
90 | interaction with the people involved, including unsolicited interaction with
91 | those enforcing the Code of Conduct, for a specified period of time. This
92 | includes avoiding interactions in community spaces as well as external channels
93 | like social media. Violating these terms may lead to a temporary or permanent
94 | ban.
95 |
96 | ### 3. Temporary Ban
97 |
98 | **Community Impact**: A serious violation of community standards, including
99 | sustained inappropriate behavior.
100 |
101 | **Consequence**: A temporary ban from any sort of interaction or public
102 | communication with the community for a specified period of time. No public or
103 | private interaction with the people involved, including unsolicited interaction
104 | with those enforcing the Code of Conduct, is allowed during this period.
105 | Violating these terms may lead to a permanent ban.
106 |
107 | ### 4. Permanent Ban
108 |
109 | **Community Impact**: Demonstrating a pattern of violation of community
110 | standards, including sustained inappropriate behavior, harassment of an
111 | individual, or aggression toward or disparagement of classes of individuals.
112 |
113 | **Consequence**: A permanent ban from any sort of public interaction within the
114 | community.
115 |
116 | ## Attribution
117 |
118 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119 | version 2.1, available at
120 | [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121 |
122 | Community Impact Guidelines were inspired by
123 | [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124 |
125 | For answers to common questions about this code of conduct, see the FAQ at
126 | [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127 | [https://www.contributor-covenant.org/translations][translations].
128 |
129 | [homepage]: https://www.contributor-covenant.org
130 | [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131 | [Mozilla CoC]: https://github.com/mozilla/diversity
132 | [FAQ]: https://www.contributor-covenant.org/faq
133 | [translations]: https://www.contributor-covenant.org/translations
134 |
--------------------------------------------------------------------------------