From c0165f72ced3f8111c3a786fad6b025ec90cdf4e Mon Sep 17 00:00:00 2001 From: damn-am-star Date: Sun, 11 Oct 2026 06:00:17 -0400 Subject: [PATCH 1/3] Add headings to rex file (#2) --- rex | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 rex diff --git a/rex b/rex new file mode 100644 index 000000000000..5d3519f51f65 --- /dev/null +++ b/rex @@ -0,0 +1,3 @@ +# A first-level heating +## A second-level heating +### A third-level heating From 4c2fd04188400d4a5935eb88d576d59523f8c23d Mon Sep 17 00:00:00 2001 From: damn-am-star Date: Sun, 11 Oct 2026 07:11:26 -0400 Subject: [PATCH 2/3] Add Developer Certificate of Origin version 1.1 Added Developer Certificate of Origin version 1.1 to the project. Signed-off-by: damn-am-star --- tor/Web | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 tor/Web diff --git a/tor/Web b/tor/Web new file mode 100644 index 000000000000..2489a7a29d86 --- /dev/null +++ b/tor/Web @@ -0,0 +1,34 @@ +Developer Certificate of Origin +Version 1.1 + +Copyright (C) 2024, 2026 The Linux Foundation and "McCoy L Stevens" "As-is" contributors. + +Everyone is permitted to copy and distribute verbatim copies of this +license document, but changing it is not allowed. + + +Developer's Certificate of Origin 1.1 + +By making a contribution to this project, I certify that: + +(a) The contribution was created in whole or in part by me and I + have the right to submit it under the open source license + indicated in the file; or + +(b) The contribution is based upon previous work that, to the best + of my knowledge, is covered under an appropriate open source + license and I have the right under that license to submit that + work with modifications, whether created in whole or in part + by me, under the same open source license (unless I am + permitted to submit under a different license), as indicated + in the file; or + +(c) The contribution was provided directly to me by some other + person who certified (a), (b) or (c) and I have not modified + it. + +(d) I understand and agree that this project and the contribution + are public and that a record of the contribution (including all + personal information I submit with it, including my sign-off) is + maintained indefinitely and may be redistributed consistent with + this project or the open source license(s) involved. From 43ae56ed00f4ed909c1738bf0da16ba41af4f584 Mon Sep 17 00:00:00 2001 From: damn-am-star Date: Sun, 11 Oct 2026 07:21:36 -0400 Subject: [PATCH 3/3] \SMS --- src/README.md | 64 --------------------------------------------------- 1 file changed, 64 deletions(-) diff --git a/src/README.md b/src/README.md index 4746402940f1..e69de29bb2d1 100644 --- a/src/README.md +++ b/src/README.md @@ -1,64 +0,0 @@ -# Welcome to our src directory - -Our application is in Node, Express, React, & Next. We are using a "subject folder" pattern. Each folder represents a major capability of the docs.github.com. To learn more about each subject, check the README.md file in the folder. - -## Why subject folders - -We used to organize our code more by role. Client, stylesheets, server middleware, shared files, tests, and so on. As the site grew, we had difficulty finding all the pieces that made a single feature work across the code base. Instead, we're moving to organize by subject. Subjects are easier to find all the related code for a single capability in one place. - -## How to create and use subject folders - -Subjects do not need every element below. Not every element needs to be a folder. A subject folder looks like: - -``` -src/ - xsubject/ - README.md - docs/ - lib/ - middleware/ - pages/ - components/ - stylesheets/ - scripts/ - tests/ -``` - -If subject depends on another subject, please make this explicit in the README. - -Choose the _most specific_ subject folder available when organizing code. - -## When to use subject folders - -A capability should have its own subject folder when it has its _own specific tests_. - -## When not to use subject folders - -A few things are harder to categorize, so there's some broad folders: - -- `frame/`, for things that make the header, footer, global sidebar functional. And there's no more specific option. -- `workflows/`, for things that are processes rather than the production application. And there's no more specific option. - -But don't hesitate to make a new subject folder if there's at least a few files related. - -## Where to get help - -Check the README.md in the subject folder for questions specific to a subject. - -For internal folks, please ask in the Docs Engineering Slack or repository. - -For open source folks, please open an issue in the repository. - -## A note on tests and required checks - -Most subject folders have their own mention in `.github/workflows/test.yml`. -Open the file to see the beginning of it. It's manually maintained but -it's important to point out two things: - -1. It's manually entered so creating a `src/foo/tests/*.ts` doesn't - automatically start running those tests. -1. When you add an entry to `.github/workflows/test.yml`, and it's - gone into `main`, don't forget to add it to the branch protection's - required checks. - -❖