File tree Expand file tree Collapse file tree 4 files changed +21
-9
lines changed Expand file tree Collapse file tree 4 files changed +21
-9
lines changed Original file line number Diff line number Diff line change @@ -19,6 +19,12 @@ please ask them in `Discussions <https://github.com/nexB/scancode.io/discussions
19
19
If you want to contribute to ScanCode.io, start with our
20
20
`Contributing <https://scancodeio.readthedocs.io/en/latest/contributing.html >`_ page.
21
21
22
+ A new GitHub action is now available at
23
+ `scancode-action <https://github.com/nexB/scancode-action >`_
24
+ to run ScanCode.io pipelines from your GitHub Workflows.
25
+ Visit https://scancodeio.readthedocs.io/en/latest/automation.html to learn more
26
+ about automation.
27
+
22
28
Build and tests status
23
29
----------------------
24
30
Original file line number Diff line number Diff line change @@ -73,15 +73,17 @@ automation methods such as a cron job or a git hook::
73
73
By providing the required environment variables in this manner, you can execute the
74
74
script with the appropriate configurations and credentials.
75
75
76
- 2. Integrate ScanCode.io with your CI/CD workflow
77
- -------------------------------------------------
76
+ 2. Integrating ScanCode.io with GitHub Workflows
77
+ ------------------------------------------------
78
78
79
- Integrate ScanCode.io seamlessly into your CI/CD workflow by using a GitHub Action,
80
- enabling automated scans as part of your development process.
79
+ Seamlessly integrate ScanCode.io into your GitHub Workflows to enable automated scans
80
+ as an integral part of your development process.
81
81
82
- A GitHub Action for ScanCode.io is currently under development. You can track the
83
- progress and updates on the development process by visiting the following link:
84
- https://github.com/nexB/scancode.io/issues/599
82
+ Visit the `scancode-action repository <https://github.com/nexB/scancode-action >`_ to
83
+ explore and learn more about the GitHub Action for ScanCode.io.
84
+ The repository provides detailed information, usage instructions,
85
+ and configuration options to help you incorporate code scanning effortlessly into your
86
+ workflows.
85
87
86
88
3. Run a Local ScanCode.io app on your machine (management commands)
87
89
--------------------------------------------------------------------
Original file line number Diff line number Diff line change @@ -138,4 +138,8 @@ Please refer to our :ref:`output_files` section for more details on the output f
138
138
How can I trigger a pipeline scan from a CI/CD, such as Jenkins, TeamCity or Azure Devops?
139
139
------------------------------------------------------------------------------------------
140
140
141
- You can use the :ref: `rest_api ` to automate your project or pipeline management.
141
+ You can refer to the :ref: `automation ` to automate your projects management.
142
+
143
+ Also, A new GitHub action is available at
144
+ `scancode-action repository <https://github.com/nexB/scancode-action >`_
145
+ to run ScanCode.io pipelines from your GitHub Workflows.
Original file line number Diff line number Diff line change @@ -31,7 +31,7 @@ class InspectPackages(ScanCodebase):
31
31
32
32
Supports resolved packages for:
33
33
- Python: using nexB/python-inspector, supports requirements.txt and
34
- setup.py manifests as input
34
+ setup.py manifests as input
35
35
36
36
Supports:
37
37
- BOM: SPDX document, CycloneDX BOM, AboutCode ABOUT file
You can’t perform that action at this time.
0 commit comments