You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE/new_detector_template.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
<!-- Please complete this new detector checklist -->
5
5
#### New Detector Checklist
6
6
7
-
-[ ] I have gone through the docs for creating a new detector [here](https://github.com/microsoft/componentdetection-bcde/blob/main/docs/creating-a-new-detector.md)
7
+
-[ ] I have gone through the docs for creating a new detector [here](https://github.com/microsoft/component-detection/blob/main/docs/creating-a-new-detector.md)
8
8
-[ ] My new detector implements `IDefaultOffComponentDetector`
9
9
-[ ] I have created a PR to the [verification repo](https://github.com/microsoft/componentdetection-verification) with components that my new detector can find
10
-
-[ ] (If necessary) I have updated the [Feature Overview](https://github.com/microsoft/componentdetection-bcde/blob/main/README.md#feature-overview) table in the README
10
+
-[ ] (If necessary) I have updated the [Feature Overview](https://github.com/microsoft/component-detection/blob/main/README.md#feature-overview) table in the README
**For bugs, issues, and support please create an issue.**
6
6
7
7
# Introduction
8
8
9
-
ComponentDetection (BCDE) is a package scanning tool intended to be used at build time. BCDE produces a graph-based output of all detected components and supports a variety of open source package ecosystems.
9
+
ComponentDetection is a package scanning tool intended to be used at build time. CD produces a graph-based output of all detected components and supports a variety of open source package ecosystems.
*[Building and running BCDE](#Building-and-running-BCDE)
15
+
*[Building and running Component Detection](#Building-and-running-Component-Detection)
16
16
*[Running in Visual Studio (2019+)](#Running-in-Visual-Studio-(2019+))
17
17
* [Running from command line](#Running-from-command-line)
18
18
* [After building](#After-building)
@@ -38,10 +38,10 @@ For a complete feature overview refer to [feature-overview.md](docs/feature-over
38
38
39
39
# My favorite language/ecosystem isn't supported!
40
40
41
-
BCDE is built with extensibility in mind! Please see our [CONTRIBUTING.md](CONTRIBUTING.md) to get started where you can find additional docs on adding your own detector.
41
+
Component Detection is built with extensibility in mind! Please see our [CONTRIBUTING.md](CONTRIBUTING.md) to get started where you can find additional docs on adding your own detector.
42
42
43
43
44
-
# Building and running BCDE
44
+
# Building and running Component Detection
45
45
DotNet Core SDK 6.0.0-rc2 is currently in use, you can install it from https://dotnet.microsoft.com/download/dotnet/6.0
46
46
We also use node and npm, you can install them from https://nodejs.org/en/download/
47
47
@@ -59,14 +59,14 @@ From the base folder:
59
59
60
60
## Using Codespaces
61
61
62
-
If you have access to [GitHub Codespaces](https://docs.github.com/en/free-pro-team@latest/github/developing-online-with-codespaces/about-codespaces), select the `Code` button from the [repository homepage](https://github.com/microsoft/componentdetection-bcde) then select `Open with Codespaces`. That's it! You have a full developer environment that supports debugging, testing, auto complete, jump to definition, everything you would expect.
62
+
If you have access to [GitHub Codespaces](https://docs.github.com/en/free-pro-team@latest/github/developing-online-with-codespaces/about-codespaces), select the `Code` button from the [repository homepage](https://github.com/microsoft/component-detection) then select `Open with Codespaces`. That's it! You have a full developer environment that supports debugging, testing, auto complete, jump to definition, everything you would expect.
63
63
64
64
## Using VS Code DevContainer
65
65
66
66
This is similar to Codespaces:
67
67
68
68
1. Make sure you meet [the requirements](https://code.visualstudio.com/docs/remote/containers#_getting-started) and follow the installation steps for DevContainers in VS Code
1. A notification should popup to reopen the workspace in the container. If it doesn't, open the [`Command Palette`](https://code.visualstudio.com/docs/getstarted/tips-and-tricks#_command-palette) and type `Remote-Containers: Reopen in Container`.
Copy file name to clipboardExpand all lines: docs/linux-scanner.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ There are 2 options for working on the Linux scanner:
13
13
**NOTE**: Docker + WSL2 is not a shortcut for this :( The bind mount is still not support even if it's created in WSL2. (See the Windows way to udnerstand why it's necessary)
14
14
15
15
1.[Using Hyper-V Quick Create](https://blogs.windows.com/windowsdeveloper/2018/09/17/run-ubuntu-virtual-machines-made-even-easier-with-hyper-v-quick-create/), create a Ubuntu virtual machine. Make sure you give it at least 30gb of storage, docker and the images use a lot of space.
Copy file name to clipboardExpand all lines: docs/renewing-secrets.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,24 +2,20 @@
2
2
3
3
Almost all of our [workflows](../.github/workflows) require secrets and those secrets can be invalidated, deleted or expired so we need to know how to renew them.
4
4
5
-
The secrets in use today in the BCDE repo can be found [here](https://github.com/microsoft/componentdetection-bcde/settings/secrets):
5
+
The secrets in use today in the Component Detection repo can be found [here](https://github.com/microsoft/component-detection/settings/secrets):
6
6
7
7
* GH_PRIVATE_REPO_PAT
8
8
9
-
## Before Starting
10
-
11
-
Verify your account has sufficient permissions. You can do this by building BCDE locally. This will verify you have access to read the packages being created and read the private BCDE repo.
12
-
13
9
## Renewing GH_PRIVATE_REPO_PAT
14
10
15
11
1. Click this link: https://github.com/settings/tokens/new
16
-
1. (Optional) Name the token BCDE_GH_PRIVATE_REPO_PAT. This will make things easier to track in the future
12
+
1. (Optional) Name the token COMPONENT_DETECTION_GH_PRIVATE_REPO_PAT. This will make things easier to track in the future
17
13
1. Check the following permissions:
18
14
* Full `repo` scope
19
15
*`read:packages` scope
20
16
1. Click **Generate token**
21
17
1. Copy and paste that token into notepad once you see it because it will disappear as soon as you leave the page
22
-
1. Enable SSO for both GitHub and Microsoft organizations for the token
23
-
1. In the [BCDE secrets page](https://github.com/microsoft/componentdetection-bcde/settings/secrets) click update on **GH_PRIVATE_REPO_PAT**
18
+
1. Enable SSO for Microsoft organizations for the token
19
+
1. In the [Component Detection secrets page](https://github.com/microsoft/component-detection/settings/secrets) click update on **GH_PRIVATE_REPO_PAT**
0 commit comments